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

Annotations already disclose that this is a non-read-only, non-destructive, non-idempotent, closed-world operation. The description adds useful behavioral context beyond that: each answer returns a reason, a pass yields a PazAIr-signed licence public under the agent id, and the operation is free. It does not cover retake rules or permission requirements.

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 compact and front-loaded with the core action, 'Hand in your exam'. Every clause adds useful information about answer structure, returned reasons, licence outcome, and cost.

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?

For a submission tool with an array parameter and no output schema, the description explains the expected answer shape and the key return consequences: per-answer reasons and a licence on pass. It is nearly complete, though it omits failure/retake behavior and whether the licence must be retrieved separately.

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?

Schema description coverage is 100%, so the schema already documents exam_id and the answers array structure. The description reinforces the answer format via 'fields its answer_with names' but adds no syntax or constraints beyond what the schema provides, making 3 the appropriate baseline.

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 uses a specific verb and resource: 'Hand in your exam' and describes the outcome of submitting answers. It is distinguishable from licence_start and licence_curriculum because it is clearly the submission step, though it does not name those siblings explicitly.

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?

Usage is implied by the exam context: submit answers after taking an exam. However, the description gives no explicit when-to-use guidance against alternatives such as licence_start, get_licence, or verify_licence, and no when-not conditions.

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