Prueba de evaluación de agentes de IA

Las respuestas y explicaciones aparecen a medida que realiza el cuestionario.

1. ¿Por qué verificar una sola respuesta final normalmente no es suficiente para los agentes?
   • Agents never produce answers
   • Agents act over many steps and cause side effects, so the path and final state matter
   • Answers are always correct
   • Reference answers cannot be written for agent tasks
2. ¿Cómo juzga SWE-bench si un agente resolvió un problema?
   • By running the repository's tests after the agent's patch
   • By counting lines changed
   • By asking the agent if it succeeded
   • By measuring response speed
3. ¿Qué mide una métrica de estilo pass^k?
   • Speed across k tools
   • Success on at least one of k attempts
   • Whether the agent succeeds on every one of k repeated attempts
   • The number of tokens per step
4. ¿Qué dimensión señalaría a un agente que tiene éxito pero toma cincuenta pasos para un trabajo de cinco pasos?
   • Task success
   • Seguridad
   • Tool naming
   • Trajectory quality
5. ¿Cuál es una debilidad conocida de los evaluadores basados en modelos?
   • No pueden leer el texto.
   • They can be biased, for example toward long or confident answers, so they need checking against human labels
   • They are always slower than humans
   • Sólo funcionan con imágenes.
6. Why reset the environment to a known state before every run?
   • So results are reproducible and runs cannot affect each other
   • To save disk space
   • Because agents require it to start
   • To make tasks harder
7. Why can public leaderboard scores mislead a team?
   • They are always faked
   • Leaderboards never publish numbers
   • Benchmarks can leak into training data, saturate or fail to match your workload
   • They only measure cost
8. How should a safety eval treat a run where the agent finished the task but obeyed a planted instruction to leak data?
   • As a full success
   • As a partial success worth half credit
   • It should be ignored
   • As a failure