List transaction requests

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

Annotations already declare read-only and idempotent safety. The description adds a valuable behavioral note that serialized transaction payloads are omitted, which sets expectations about the response and hints that get_transaction_request should be used for payloads.

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?

One sentence with the core purpose and a critical omission note. No wasted words.

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?

The tool is simple, but with no output schema and no mention of the statuses filter, the description leaves gaps. It tells what is omitted but not what is included, and doesn't explain filtering behavior.

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?

The single parameter 'statuses' is entirely undocumented in the description, and schema coverage is 0%. The enum values are self-explanatory, but the description adds no meaning about how filtering works or what the parameter does.

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?

The description clearly states the tool lists recent approval requests, using a specific verb and resource. It distinguishes from siblings like get_transaction_request (single fetch) and request_* (creation) by its list nature.

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 description does not explicitly state when to use this tool versus alternatives. It implies a browsing use case with 'recent' but offers no guidance on filtering by status or when to prefer get_transaction_request for specific details.

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