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

With no annotations, the description carries the burden of disclosure. It explicitly states 'Free, no authentication required' and describes the output (allowed amount) and a return field (pageUrl). This adds meaningful behavioral context beyond the schema, though it does not cover error handling or return format.

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?

Four concise sentences, each serving a distinct purpose: defining the output, providing a use case, stating access requirements, and giving result-handling guidance. No redundancy, and the primary function is front-loaded.

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?

For a simple one-parameter lookup with no output schema and no annotations, the description is adequate. It covers output definition, use case, access, and a key return field. It omits potential error scenarios or return structure details, but these are less critical for this complexity level.

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 a clear pattern and description for the cpt parameter. The tool description adds background about the CMS Physician Fee Schedule but does not add parameter-specific syntax beyond what the schema already provides.

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 a specific verb ('Returns') and resource (Medicare national-average non-facility allowed amount for CPT/HCPCS codes). It distinguishes from sibling tools like lookup_hospital and audit_medical_bill by focusing on rate benchmarking.

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?

Provides a clear use case: benchmarking what a hospital or clinic billed against Medicare reimbursement. Also gives guidance for using the pageUrl for patient-facing disputes information. Does not explicitly name alternative tools, but context strongly implies when to use it.

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