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

Annotations already establish read-only and non-destructive behavior. The description adds meaningful context beyond annotations: it is a live NPPES lookup, returns specific fields, is cryptographically attested, and carries a $1.00 USDC cost. It does not cover error behavior or rate limits, but the read-only annotation lowers the burden.

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 compact and front-loaded with the primary use case. The source, attestation, verification URL, and pricing all add useful selection context. Nothing is redundant, though the attestation details are slightly promotional.

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?

The description tells the agent what the tool returns and when to use it, but it omits guidance on parameter usage, optionality, and edge cases such as failed lookups. For a read-only tool with no output schema, the description is adequate but not complete enough to guarantee correct invocation beyond the obvious npi parameter.

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% and the description does not explain the parameters' roles except indirectly through 'NPI' and 'license state.' It does not clarify how state or provider_name affect the lookup, whether any parameter is required, or what combinations are valid. With no schema descriptions, the description needed to compensate and largely does not.

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 names a specific verb and resource: verifying a clinician or organization NPI against CMS NPPES. It grounds the use case in contracting and credentialing, and the mention of NPPES clearly differentiates it from the many 'benchmark' sibling 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 explicitly states when to use the tool: when verifying an NPI against CMS NPPES before contracting or credentialing. It does not list exclusions or name alternative verification tools, but the context is clear enough for an agent to select it appropriately.

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