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

With no annotations, the description carries the full transparency burden. It clearly discloses what the tool returns, including conditional content ('Reviewed records also include...') and a free practice-exam link. It implies a read-only operation by the nature of 'get', though it does not explicitly state there are no side effects, rate limits, or auth requirements. It is transparent enough for an agent to know what to expect.

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 moderately detailed but every sentence contributes: first enumerates the blueprint's contents, then adds conditional extras, then gives example queries, then clarifies the input, then notes the practice link. It is front-loaded with the core purpose and avoids redundancy. It is slightly longer than strictly necessary but not bloated.

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 single-parameter read tool with no output schema or annotations, the description is thorough. It covers what data is returned, the conditional additional records, valid input forms, and a bonus (practice link). It does not explicitly describe error conditions or the exact result format, but those are minor for a simple get operation. The description is complete enough for an agent to confidently call the tool.

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 input schema already has a 100% description coverage for the single 'exam' parameter, stating 'Exam id, exam code, or certification name'. The description repeats exactly that information ('Accepts an exam_id, exam_code, or certification name') without adding new syntax, format, or edge-case details. Since the schema already handles the semantics, the description adds no extra value, matching the baseline of 3.

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 ('Get'), resource ('full published blueprint for ONE certification exam') and enumerates the exact contents (domain/objective breakdown, passing score, question count, duration, price, prerequisites, policy, languages, source URL). This makes the purpose unmistakable, and the emphasis on 'ONE exam' differentiates it from sibling tools like compare_exams.

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 provides explicit trigger phrases ("Call this for 'what's on the X exam', 'how is X weighted by domain'...") that tell an agent exactly when to invoke it. However, it does not mention alternatives or when NOT to use it, such as directing to search_exams for discovery or compare_exams for multiple-exam comparisons. The single-exam scoping is implicit rather than explicit.

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