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

The description discloses that the tool returns a price breakdown including cost, consultation fee, shipping, and discounts, and notes that plan durations vary by medication. Since annotations already declare readOnlyHint, the description adds context about response content and dependencies, but doesn't mention rate limiting or error 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?

The description is compact at three sentences, front-loaded with the main action, then return value, then usage note. No unnecessary words or repetition.

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 presence of an output schema and readOnlyHint annotation, the description covers the essential input caveat (plan duration variation) and lists supported medications. It is complete and self-sufficient for the tool's purpose.

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 already includes descriptions for all four parameters, so baseline is 3. The description adds the important nuance that plan_months values vary by medication and that medications_details should be consulted first, which is semantic information not fully captured in the schema's simple '1, 4, or 6' description.

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 'Get detailed pricing for a specific medication, form, and plan duration' with a specific verb and resource. It distinguishes itself from sibling tools like medications_details and medications_availability by focusing on pricing and specifying the return breakdown.

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?

It explicitly directs users to 'use medications_details first to see available plan_months values,' providing a concrete workflow. It also clarifies scope by listing supported medications, effectively guiding when to use this tool.

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