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

Annotations already communicate read-only, idempotent, and non-destructive behavior, so the description does not need to restate those. It adds genuinely useful behavioral context: per-area results, FAA-weighted scoring for Part 107, pass-mark comparison, correct answers with explanations, and a suggested next step. There is no contradiction with the annotations.

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 a single, front-loaded sentence that begins with the core action and then packs the return-value details into a clear list. Every clause carries meaningful information and there is no filler.

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?

There is no output schema, so the description reasonably enumerates what the tool returns: overall and per-area scores, weighted Part 107 scores, areas below pass mark, explanations, and a next step. It omits error-case behavior and answer-format details, but for a read-only scoring tool with annotations already covering safety, the context is largely complete.

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 documents the exam enum values well, but the answers parameter is only described as an array in the schema, and the description adds little beyond 'a set of answers' and 'each question.' With only 50% schema coverage, the description should compensate for the missing answers semantics, but it does not explain how answer values map to question_id or what constitutes a valid answer.

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 action and resource ('Scores a set of answers to a Rotate Pilot readiness diagnostic') and enumerates the outputs in detail, including the Part 107 weighting nuance. It is clearly distinguishable from siblings like check_answer and practice_questions, though it does not explicitly name them.

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 description implies the tool is for scoring a full answer set from a readiness diagnostic, and the required exam and answers parameters reinforce that context. However, it does not explicitly say when to use this tool over alternatives such as check_answer or diagnose, nor does it state any exclusion criteria.

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