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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered by structured data. The description adds the underlying endpoint (GET /search/transactions) and the returned field set, but says nothing about pagination behavior, result ordering, or rate limits beyond what the schema already documents via starting_after and sort.

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?

Two dense sentences with no filler: the first front-loads what the tool returns, the second covers filtering, and the endpoint is tacked on last as a compact reference. Every clause carries information.

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?

With 16 optional parameters, no output schema, and full schema descriptions, the description is complete enough for correct invocation, and it usefully compensates for the missing output schema by listing returned fields. It stops short of covering pagination semantics and default ordering, which an agent would need for multi-page iteration.

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 all 16 parameters carry their own descriptions, so the schema does the heavy lifting. The description's filter list (type, method, form, order, donor, dates) merely restates a subset of the schema's parameters without adding syntax or format detail, making the baseline 3 appropriate.

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 a specific verb and resource ('List payment transactions (money movements)') and enumerates the returned fields (amount, deductible amount, currency, type, payment method, masked card, status, form, donor email), so the agent knows exactly what resource this is. It does not explicitly contrast with get_transaction or list_orders, so it falls just short of 5.

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?

The second sentence tells the agent what can be filtered (type, method, form, order, donor, dates), which implies when the tool is appropriate, but there is no explicit when-to-use or when-not guidance and no named alternative for single-record lookups (get_transaction). Usage is inferable rather than stated.

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