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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false, indicating a safe, read-only operation. The description adds value beyond annotations by noting the 'bounded API-order sample' nature and clarifying that 'Payments are not provider revenue or margin,' which is critical for correct interpretation of the data. No contradictions.

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?

Two sentences with no waste. The first sentence states the primary purpose and scope. The second is a critical disclaimer. Content is front-loaded and efficient.

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 the tool has 5 parameters and an output schema, the description covers purpose, sample behavior, count, and a key payment caveat. It does not explain pagination (limit/offset) or output structure, but an output schema exists. For a simple list tool with robust annotations, this is adequately complete.

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 0%, so the description must compensate. It mentions service_type, year, and state indirectly, but does not describe limit or offset (bounded sample implied). The description adds only partial parameter meaning; parameters like limit and offset are not explained. The example in schema helps, but the description alone is insufficient for an agent to understand all parameters.

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 it returns a bounded sample of Medicare post-acute provider rows for home health, hospice, or skilled nursing by year and optional state, with an authoritative count. It also clarifies that payments are not revenue/margin. This verb-resource combination is specific and distinguishes it from sibling tools like medicare_post_acute_trend (trend data) and other market tools.

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 context (getting provider rows for specific service types, year, state) but does not explicitly state when to use this tool vs alternatives, nor does it provide exclusions. Sibling tool names like medicare_post_acute_trend suggest aggregate trend data, but no explicit guidance is given.

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