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

The annotations already declare readOnly=true, idempotent=true, destructive=false, openWorld=false, so the safety profile is fully carried by structured data and the bar is lower. The description adds no further behavioral context — nothing about default ordering, pagination behavior (even though limit/offset exist), or result volume — so it earns no credit above the annotated baseline.

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?

A single well-formed sentence with no filler and the resource front-loaded. It is efficient, though the content is largely a recap of parameters the schema already documents.

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 9-parameter tool with a nested date_range object and no output schema, the description is thin: it says nothing about return shape, default ordering, pagination semantics, or how results relate to search_transactions. An agent could invoke it, but not confidently predict or scope the output.

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 89%, so the schema already documents every filter, its format (ISO dates, IDs, substrings) and the limit default/max. The description's filter list merely restates the schema's parameter names and adds no semantics, so the baseline 3 applies.

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?

Specific verb+resource (list transactions) with an enumeration of the filterable dimensions, which lets an agent recognize it as a filtered collection read. However, it never distinguishes itself from the sibling tools search_transactions or get_transaction, so an agent cannot tell from the description which one to reach for.

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?

'Optional filters for...' implies a retrieval-with-filtering use case and makes clear that all criteria are optional, but there is no explicit when-to-use/when-not guidance and no steering toward search_transactions versus this tool.

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