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

Annotations already establish that this is a safe, read-only, closed-world, idempotent operation. The description adds meaningful behavioral context: ranking by cost per 30 days, inclusion only when the supply purchased is stated, and disclosure of referral-commission status plus source and terms pages.

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 front-loaded with the primary purpose and ranking rule, and every phrase adds relevant information. It is somewhat dense in the return-value listing, but there is little wasted wording.

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 carries the return-value burden and does so thoroughly, listing seller, product, cost, check date, source page, commission indicator, and terms page. It also explains input forms and ranking constraints, leaving only minor implementation details to the schema.

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 the schema already documents both parameters. The description still adds useful meaning by explaining that medication accepts a brand, an ingredient (which expands to brands and compounded lists), or a compounded product, with concrete examples.

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 states a specific resource (lowest current US self-pay GLP-1 prices ranked by cost per 30 days) and clarifies accepted input forms. It is clearly a broad price lookup rather than a seller-specific lookup, but it does not explicitly distinguish itself from the sibling tools by name.

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?

Usage is implied through the accepted medication forms and the constraint that only prices stating supply are ranked. However, it does not explicitly say when to use this versus find_seller_glp1_prices or list_glp1_medications, nor does it provide exclusions.

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