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

Annotations already mark it read-only, idempotent, and non-destructive, and the description adds meaningful behavior: it is educational only, returns a general exam guide for conditions without a file guide, includes diagnostic code and rating criteria only when a guide exists, and cannot take actions like scheduling or contacting VA. No contradictions with 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 front-loaded with the trigger and a compact list of return contents, then adds boundary statements that prevent misuse. Every sentence contributes useful information, and the length is proportionate to the tool's educational scope.

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?

Even without an output schema, the description enumerates what the tool returns, explains the conditional behavior for guides, and clarifies what it will not do. For a read-only educational reference tool, this provides enough context for an agent to select and invoke it correctly.

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 baseline is 3. The description indirectly reinforces the 'condition' parameter by explaining condition-specific behavior, but it does not add any detail about 'currentRating' beyond the schema's own explanation. The schema carries the parameter documentation burden adequately.

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 opens with a specific trigger ('a veteran has a VA compensation and pension examination scheduled') and states exactly what the tool returns: exam type, length, examiner actions, common questions, DBQ sections, and records to bring. It clearly distinguishes itself from sibling tools by focusing on exam preparation rather than ratings, eligibility, or legal authority.

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?

It explicitly says when to use it ('Use this when a veteran has... scheduled') and provides important exclusions: it does not give advice about what to describe, does not schedule/reschedule/contact VA, and does not decide ratings. It does not name a specific sibling alternative, so the when-not-to-use guidance is implied rather than explicit.

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