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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the semantic grain (payment vs order level), but says nothing about pagination behavior, result volume, or auth expectations. With annotations carrying the safety burden, a 3 is appropriate.

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?

Five short sentences, each load-bearing: identity + UI location, grain clarification, example queries, filter inventory, and the alternative route. The disambiguating grain statement is front-loaded immediately after the opening rather than buried.

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 read-only filtered-list tool with full schema coverage and safety annotations, the description is nearly complete and no output schema is needed. The one gap is sibling overlap: it claims to cover 'refunds' while hub_get_refunds also exists, and it never clarifies the split.

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%, so every parameter (including page/pageSize limits and the date-inclusivity rule) is already documented. The description's filter list ('payment method, processor, card provider or status, or search by order number') maps onto existing parameters but adds no syntax or format detail beyond the schema. Baseline 3.

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 resource (individual transactions) with an explicit grain clarification: 'This is the PAYMENT level, not the order level: one order can hold several transactions.' It also names the sibling it is not (get_financial_summary), so an agent can separate payment-location from sales-figures work without opening either schema.

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?

Gives concrete when-to-use phrasings ('find the payment for receipt 1042', 'which transactions failed') and an explicit when-not with the alternative named: 'For sales figures use get_financial_summary — this tool is for locating a specific payment.' Routing to the correct tool is unambiguous.

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