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 covered. The description adds genuinely useful behavior: the exact payload fields returned (NPI, NCPDP, address, phone, fax) and the GraphQL source ('pharmacies'), which matters because there is no output schema. It omits pagination/result-cap behavior.

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?

A single dense sentence that front-loads the resource, then the filter facets, then the return payload. No filler or redundant restatement of the title.

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?

With no output schema, the description usefully enumerates return fields, and with zero required params it correctly conveys that all filters are optional ('and/or'). It leaves pagination parameters (first, offset) to the schema, which is a minor gap.

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 baseline is 3, but the description adds meaning beyond the schema by interpreting the enum ('PICK_UP = retail, MAIL_ORDER'), specifying that radius is in miles and paired with latitude/longitude, and framing name as partial matching. It does not explain first/offset pagination semantics.

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 (Search) and resource (pharmacies) plus the three search axes: name, geo-radius, and fulfillment type. It also names the returned identifiers (NPI, NCPDP). It does not explicitly distinguish itself from the sibling photonhealth_get_pharmacy (single-record fetch), so it falls short of a 5.

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 when to use the tool by enumerating searchable facets ('by name and/or near a location', 'by fulfillment type'), which tells an agent it is for filtered discovery. However, there is no explicit when-not guidance, no mention of combining filters, and no routing to/away from photonhealth_get_pharmacy.

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