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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safe, static read profile is covered. The description adds that the price list covers specific tiers and currency, which is useful content context, but says nothing about whether the data is cached, region-specific, or subject to change — beyond-annotation value is modest.

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 front-loaded sentence with no filler. The trailing clause 'per-case work for a single chargeback of $10,000 or more' is grammatically ambiguous — it is unclear whether $10,000 is a price or a minimum case size — which costs it the top mark.

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 zero-argument, read-only lookup with no output schema, the description gives enough to know what categories of pricing come back and in what currency. It does not list actual amounts or the two plan names, but enumerating those is the call's job, not the description's.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description's mention of USD implicitly clarifies that no currency parameter is expected.

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?

Names the specific resource (representments.com pricing) and the currency (USD), and enumerates the three price categories returned: the free first response, two monthly plans, and per-case work. An agent can tell this apart from the sibling reason-code and help tools without opening the schema. Slightly weaker than a 5 because it is written as a noun fragment rather than 'Returns pricing for...'.

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?

No guidance on when to call this versus doing something else, and no statement of preconditions. The sibling tools (get_help_with_a_dispute, list_reason_codes, lookup_reason_code) are unrelated, so the risk of misrouting is low, but the description offers no explicit usage cue at all.

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