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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only the endpoint path and the returned field set, with no note on pagination behavior, result caps, or default ordering beyond what the schema documents.

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 sentences, front-loaded with the resource, then the payload fields, then the filters, with zero filler. Slightly dense but every clause maps to a real capability.

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 and no output schema, the description usefully enumerates what comes back (amount, currency, masked card, status, buyer email), which the schema cannot convey. It stops short of explaining pagination or default page size, both of which live only in the schema.

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 one of the 16 parameters is already documented, making 3 the baseline. The description's filter recap adds enum examples for type but also drifts slightly by naming 'donor', which does not match any parameter name (customer_id/email).

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 ('List payment transactions (money movements)') and enumerates the returned fields and filterable dimensions, so the agent knows exactly what data this tool surfaces. It does not explicitly distinguish itself from the singular sibling ticketspice_get_transaction, which keeps it off a 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?

Usage is implied rather than stated: 'Filter by type, method, form, order, donor or dates' tells the agent it is the search tool, but there is no explicit when-to-use versus ticketspice_get_transaction or when-to-prefer listing orders instead.

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