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

Annotations already establish readOnlyHint=true and openWorldHint=true. The description adds valuable behavioral context by enumerating what the returned record includes—monthly total, inclusions, per-drug prices, first-month deal, lock-in terms, and What you get facts—though it does not describe error behavior for invalid slugs.

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 a single front-loaded sentence with no filler, efficiently listing the returned record's contents. The phrase 'What you get facts' is slightly awkward, but overall it is concise and well structured.

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 one-parameter read tool with no output schema, the description does a good job explaining what data comes back. It leaves minor gaps around invalid-slug behavior and direct sibling comparisons, but annotations already cover the safety profile.

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%, and the schema already explains the slug parameter and points to get_programs for listing identifiers. The description adds no parameter-level meaning beyond what the schema provides, so the high-coverage baseline of 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?

The description clearly states that this returns the full verified pricing record for one GLP Chart program, including specific fields such as total monthly cost, per-drug prices, and lock-in terms. It is specific about the resource and scope, though it does not explicitly differentiate itself from siblings like fair_price or cheapest.

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: use this to get detailed pricing for a single program identified by slug. However, the description gives no explicit when-to-use guidance versus alternatives such as fair_price, cheapest, or coverage, and no exclusions.

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