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

With no annotations provided, the description must convey behavioral traits. It mentions the source and price, and correctly implies a read-only search. However, it omits details about pagination (offset/limit), ordering, error behavior, or what happens with no results. The price note adds some transparency.

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 extremely concise (two sentences plus metadata), with key information front-loaded ('Search Medicare providers...'). Every element adds value—verb, criteria, purpose, data source, and pricing. No wasted words.

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 11 parameters and no output schema, the description is insufficient. It does not explain return format (what fields are returned for providers?), how offset/limit affect results, or how the min/max range parameters interact. The source and price are helpful, but the description does not cover the full complexity of a search tool with extensive filters.

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 lists criteria groups (NPI, state, specialty, volume, beneficiaries, payments) but does not explain the min/max variants for numeric fields or the behavior of limit/offset. The mapping to schema parameters is partial and lacks detail, leaving significant ambiguity for an 11-parameter tool.

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 uses a specific verb ('Search Medicare providers') and lists multiple criteria (NPI, state, specialty, service volume, beneficiaries, payments), clearly distinguishing it from sibling search tools like hcris_hospital_search or nppes_enumeration_search. It also specifies the source (CMS Medicare claims), which adds context.

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 finding providers matching certain criteria but does not explicitly state when to use this tool versus alternatives (e.g., nppes_enumeration_search for NPI lookups, or other provider-specific searches). No exclusions or comparative guidance are provided.

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