count_appeal_precedents_for_rejection_code

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds valuable context: it is a 'signal-only' summary, 'reference only', and historical signal does not predict future outcomes. No contradiction 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 well-structured: main functionality first, then usage guidance, then caveats and attribution. While slightly long, every sentence serves a purpose and the core message is front-loaded. Could be marginally more concise but remains effective.

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 no output schema, the description adequately explains the output components (volume bucket, win-rate, review stages) and the reference nature. It also covers the tool's purpose and limitations. Missing exact output keys or types, but sufficient for an agent to understand what to expect.

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% with descriptions for both parameters. The description reinforces the requirement that at least one must be provided, gives character length examples (e.g., '0312A', '86008C'), and clarifies the optional nature. This adds moderate value beyond the schema.

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 aggregates a summary of dispute resolutions for a given NHI rejection code or procedure code, specifying the output (volume bucket, win-rate signal, review stages). It also distinguishes from the sibling tool lookup_appeal_statistics_by_category, which provides broader landscape data.

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?

Explicitly provides 'Use when' (triaging contesting a specific code) and 'Don't use' (fetching individual case details) guidance, and directs to an alternative (lookup_appeal_statistics_by_category) for broader analysis. This leaves no ambiguity about when to invoke this tool.

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