list_transactions

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

With no annotations, the description must carry the behavioral burden. It usefully discloses cursor-based pagination and that results are trimmed transaction objects, but omits permissions/auth needs, rate limits, and what 'trimmed' actually excludes. Partial but real added context beyond 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?

Two sentences, front-loaded with the verb and scope, followed by a compact enumeration of filters. The middle clause is dense and comma-laden but each element maps to a real parameter, so little is wasted.

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 an 11-parameter list tool with no output schema, the description should explain the return shape more concretely; 'trimmed transaction objects' leaves the agent guessing what was removed. Pagination is mentioned but cursor semantics are only in the schema, making this adequate rather than complete.

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 is already documented with formats, ranges, and defaults. The description merely enumerates the same filter names without adding format rules or interaction 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?

States a specific verb (Retrieve) and resource (transactions) with scope (across all accounts) and notes advanced filtering capability. However, it never names or contrasts with the close sibling list_account_transactions, so differentiation rests on the reader noticing 'all accounts' versus the sibling's account scoping.

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 when-to-use guidance, no exclusions, and no reference to alternatives. With siblings like list_account_transactions, get_transaction, and get_treasury_transactions present, the agent gets no help deciding which to call; usage is only implied by the 'all accounts' phrasing.

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