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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds some scoping context by specifying organization types and name-based search, but it does not disclose additional runtime behaviors such as result format, pagination, or whether matching is exact or partial. The description does not contradict the annotations.

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 two short sentences with no filler. It front-loads the main action and resource, then immediately states required and optional parameters. Every part earns its place.

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 read-only search tool with one required parameter, the combination of description, schema, and annotations is largely sufficient for an agent to call it correctly. It could be strengthened by naming the data source or clarifying result behavior, and there is no output schema, but these are not critical gaps for this tool.

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%, with clear descriptions for organization_name, city, state, and limit. The description mostly restates what the schema already defines (organization_name required; state and city optional) without adding new semantic details or edge-case guidance.

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'), a clear resource ('healthcare organizations'), and helpful examples ('hospitals, clinics, group practices, labs'). It clearly indicates a name-based lookup for organizations, which implicitly differentiates it from provider-focused siblings like npi_search_provider, but it does not explicitly name or contrast those alternatives.

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 states the required parameter (organization_name) and the optional filters (state, city), which gives the agent a clear precondition for calling the tool. However, it provides no explicit guidance on when not to use this tool or which sibling tool should be used instead, so the routing guidance is mostly implied rather than stated.

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