Exam Picture Score

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry the full behavioral burden. It describes the scoring categories and tally output, but does not state whether the operation is read-only, whether it mutates state, what permissions are required, or how errors are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action and stays in a single dense sentence. It is efficient, though the long enumeration of scoring details makes it harder to parse than necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be fully explained. However, the required input parameter 'out' is undocumented, there are no annotations, and the description provides no operational guidance about side effects or prerequisites, leaving too much unknown for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has one required parameter, 'out', with 0% schema description coverage, and the description never mentions or explains it. An agent cannot determine what value to pass for 'out' from either the schema or the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: scoring the last answers of an exam_picture_round against its key. It also distinguishes the action from running the round by focusing on post-round evaluation and per-card/tally outcomes. Some domain jargon reduces immediate clarity, but the core purpose is clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'last answers of an exam_picture_round' implies this is used after an exam_picture_round has produced answers, giving contextual usage. However, it does not explicitly say when to use this versus related tools such as exam_eye_score or exam_check, nor does it provide exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.