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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds useful context about the data volume (~1.8M entries) and searchable fields (name, NPI, city), but does not contradict annotations. Behavioral disclosure is adequate given the annotation coverage.

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 front-loaded with examples, then provides the functional description in a concise format. Every sentence adds value without extraneous text.

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 4 parameters, no output schema, and high schema coverage, the description adequately covers the tool's purpose and search capabilities. The note 'same shape as npi_individual' provides indirect output structure context. It is sufficiently complete for an agent to use correctly.

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%, so the baseline is 3. The description adds minor value by specifying that terms can include city (beyond schema's 'canonical names') and clarifying default behavior for df. However, it does not significantly enhance understanding beyond the schema.

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 the tool is for searching the NPPES NPI registry for organizational providers like hospitals and group practices. It includes specific verb phrases ('Find a hospital / clinic by name', 'look up NPI for [organization]') and distinguishes from the sibling tool npi_individual by noting the same shape but for organizations.

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 provides clear usage scenarios (e.g., 'verify a healthcare facility') and mentions that terms can be org name, NPI, or city. While it references npi_individual as 'same shape,' it does not explicitly state when to use one over the other, but the context and sibling listing make it inferable.

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