Transactions List Transaction Attachments

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

Annotations already indicate readOnly, openWorld, and idempotent behavior. The description adds no behavioral context beyond the bare operation: it does not say whether the response contains metadata, file content, pagination details, or how redirect_posted affects results. No contradiction exists, but the description contributes no additional transparency.

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?

The description is a single concise sentence with no redundant wording. It is front-loaded with the verb and resource, though it achieves conciseness at the expense of substantive guidance.

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 no output schema and an unclear parameter like redirect_posted, the description is too sparse. The agent is left without enough context to understand response structure, pagination behavior, or the impact of optional parameters.

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 50%, with fields and output_mode documented in the schema, but transaction_id and redirect_posted lack parameter descriptions. The tool description itself adds no meaning for any parameter, so it does not compensate for the undocumented parameters.

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 states a specific verb and resource: 'List transaction attachments.' This clearly distinguishes it from attachment operations like get, upload, download, and delete. However, it does not explicitly differentiate itself from the sibling transactions_get_transaction_attachment beyond the singular/plural distinction.

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 guidance is given for when to use this tool versus alternatives such as transactions_get_transaction_attachment, transactions_download_transaction_attachment, or transactions_list_transactions. There is no mention of context, prerequisites, or exclusions.

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