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

Annotations already cover readOnly, idempotent, and non-destructive, so the safety profile is settled. The description adds genuine substance beyond that: it discloses the return payload's structure (all payment methods, the retry loop, what's always free, per-use-case recommendations) and notes it mirrors /api/payment.json, which lets an agent reason about freshness and content.

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?

Effectively two sentences: a front-loaded statement of purpose with an enumerated payload, then a pointer to the equivalent HTTP endpoint. Every clause carries information. It is dense but not padded.

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?

An output schema exists, so return-value explanation is not owed, and with zero parameters there is no input surface to cover. What remains missing is sibling differentiation against get_pricing and check_access, the only thing an agent could still get wrong.

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 correctly says nothing about inputs rather than inventing any.

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 ('Return the agent payment manifest') and enumerates the concrete contents: payment methods, the 402 retry loop, free items, recommended paths. An agent knows exactly what comes back. However, it does not distinguish itself from siblings get_pricing, check_access, or get_access_info, which cover overlapping payment/access territory.

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 rather than stated: mentioning 'the exact 402 retry loop' signals you call this when you need to know how to pay, but there is no explicit 'use this when / use X instead' guidance. With get_pricing and check_access as siblings, the absence of routing guidance is a real gap.

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