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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds the underlying endpoint and open-world search semantics, but discloses nothing about pagination behaviour, result caps, or what an empty match returns — though the pagination contract is picked up by the schema.

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 core verb is front-loaded, but the second half of the first sentence ('optionally filtered by status') restates the earlier 'by status' and wastes the limited space on redundancy rather than useful differentiation. The trailing endpoint reference is filler for an agent.

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-required-parameter, read-only search with full schema coverage and a strong annotation set, the definition is nearly sufficient — the endpoint, matching fields and filter are present. The only real miss is routing guidance against list_disputes/get_dispute, which for a 35-sibling surface is a meaningful gap.

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 each of the five parameters carries a meaningful description, so the schema does the heavy lifting. The description's mention of status and exact charge token marginally maps to query/status but adds no syntax, format, or matching-rule detail beyond what the schema states.

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 ("Search disputes") and hints at the searchable fields (status, exact charge token), which distinguishes it from the sibling write-free getters. However it never explicitly contrasts with pinpayments_list_disputes, and the phrase 'by status ... optionally filtered by status' is self-duplicating and muddies what is actually being matched.

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 use this versus pinpayments_list_disputes or pinpayments_get_dispute within the large sibling set. The only implicit cue is 'exact charge token', leaving the agent to infer that this is the lookup path for a known charge token rather than a general listing.

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