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

Annotations already establish this as a read-only, idempotent, non-destructive, closed-world operation, and the description adds real behavioral context on top: it does not schedule or contact VA, examiner findings and VA (not this tool) decide the rating, and it deliberately does not return coaching advice on what to describe, emphasize, or omit. That is exactly the extra, non-structured context an agent needs.

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 trigger is front-loaded, followed by return contents and then limits, which is the right ordering. It runs long and the enumeration of returned fields is dense, but nearly every clause carries information an agent would otherwise have to guess.

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?

With no output schema, the description carries the full burden of describing the return value and does so comprehensively: exam type and length, examiner actions, common questions, applicable DBQ sections, records to bring, diagnostic code, and rating-criteria location. For a two-parameter read-only tool, an agent has everything needed to call 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 coverage is 100%, so the baseline is 3, but the description adds meaningful semantics about the 'condition' parameter: a condition with a guide on file also returns its diagnostic code and where its rating criteria are published, while any other condition yields a general exam guide. The optional 'currentRating' parameter for increase exams is only documented in the schema, not the description, so it falls short of a 5.

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?

States a specific verb and resource ('Prepare for a C&P exam') plus the scope of the condition and what it returns. It is clearly distinguishable from siblings like find_claim_help, get_guide, and search_guides because it is scoped to a scheduled examination, not general claim help or guide lookup.

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?

Gives an explicit trigger ('when a veteran has a VA compensation and pension examination scheduled for a condition and wants to know what it involves') and explicit exclusions (it does not schedule, reschedule, or contact VA). It stops short of naming which sibling to use when the veteran instead needs claim help or general benefits information.

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