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

Annotations already indicate read-only, idempotent, non-destructive; description adds data source (Loa's hospital price-transparency dataset) and aggregation nature. No contradictions. Output schema exists so return format is covered.

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: first explains what tool does and data source, second gives usage guidance. Front-loaded, concise, no fluff.

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 tool has 3 parameters, full schema coverage, and output schema, description provides sufficient context: purpose, data source, when to use, and implicit alternatives. No gaps.

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 clear descriptions for each parameter (state, zip_code, cpt_codes). Description does not add new param details beyond what schema provides, so baseline 3 is appropriate.

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?

Description states it returns market cash/self-pay and insurance-negotiated price summaries for CPT codes, aggregated from Loa's dataset. It distinguishes from siblings by positioning as 'preferred benchmark' and contrasting with 'single-hospital rate', making purpose clear.

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 says 'Use this when the user wants source-grounded regional or national market pricing rather than a single-hospital rate', providing clear context for when to use. Does not list exclusions but sibling tools imply alternatives.

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