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

Annotations already declare readOnlyHint and openWorldHint, so the bar is lower, and the description adds real context: restrictions stem from pharmacy licensing, the response carries a reason when unavailable, and ambiguous names fan out into an 'options' array. It does not mention rate-limit behavior despite the client_ip parameter, but the safety and result-shape profile is well covered.

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?

Purpose and the licensing rationale are front-loaded, then the return semantics follow. The final sentence about 'options' is long but earns its place by explaining ambiguous-name behavior; nothing is redundant.

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 an output schema present, the description needn't enumerate return fields, and it still flags the key ambiguity case and the unavailable-reason. Combined with 100% parameter coverage, an agent has what it needs to call this 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 description coverage is 100%, so the state, client_ip, and medication parameters are already documented, including the example formats. The description only implicitly adds that medication names may map to multiple treatments; it gives no format or matching-rule detail beyond the schema, so 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 (check medication availability for shipping to a patient's state) and scopes it geographically. It is clearly separable from siblings like medications_list, medications_details, and medications_pricing, which supply catalog and price data rather than shipping eligibility.

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 gives clear context for when this tool applies: verifying ship-to-state eligibility, including compounded-medication licensing restrictions. It also points at medications_list as the source of a medication id, but never states exclusions or when a sibling should be used instead.

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