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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds nothing behavioral beyond that — no note on result truncation, the default/limit behavior, pagination, or data source recency. It essentially restates the schema's required/optional split.

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 short sentences, zero filler, with the action and resource front-loaded and the required-parameter constraint placed second. Nothing could be cut without losing information.

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 four-parameter, read-only search tool with full schema coverage and annotations covering safety, the description supplies enough to invoke it correctly. The one gap is the absence of sibling disambiguation against npi_search_provider/npi_search_specialty, and no hint about result-set behavior.

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 100%, so all four parameters (including the limit range and state code format) are already documented in the schema. The description only repeats that organization_name is required and state/city optional, adding no syntax or semantic detail beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('Search healthcare organizations') and enumerates the resource types (hospitals, clinics, group practices, labs), so the agent knows what it returns. It does not, however, distinguish itself from the close siblings npi_search_provider and npi_search_specialty, which also live in the NPI namespace.

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?

'By name' plus 'Requires organization_name' implies the usage context — a name-based organization search — but there is no explicit when-to-use, no exclusion of the provider/specialty search siblings, and no statement about what to do if the name is unknown. Usage is inferable rather than stated.

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