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

Annotations already declare readOnlyHint and idempotentHint, so the description's main addition is clarifying the educational nature and non-predictive role. This adds useful context beyond annotations, ensuring agents understand it is statistical analysis, not a decision tool.

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 three sentences with no redundant text. It front-loads the action and output, then adds value with usage context and disclaimers. Every sentence contributes meaningfully.

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?

Given complexity and output schema existence, the description covers core functionality and output nature. However, missing parameter explanations for is_pact_act and sample_limit, and lack of detail on return structure (though output schema may compensate), leave the tool only partially complete for agent use.

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?

With only 20% schema description coverage, the description names three of five parameters (conditions, service-connection theory, toxic-exposure basis) but omits 'is_pact_act' and 'sample_limit'. It does not explain enum values or parameter constraints, leaving significant gaps for agent understanding.

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 clearly states the tool's purpose with specific verbs ('analyze') and resources ('similar real BVA decisions'), detailing output (grant/deny/remand breakdown, grant rate, examples). It distinguishes itself from siblings like 'search_bva_decisions' by emphasizing similarity analysis and educational statistics.

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 usage for understanding trends in similar appeals ('how have appeals like mine gone'), but does not provide explicit when-to-use or when-not-to-use guidance compared to sibling tools. It includes a caveat about not being prediction/legal advice, which helps, but lacks explicit alternatives or exclusions.

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