Transactions Get Transaction

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

The description adds no behavioral information beyond what the annotations already provide. While annotations indicate a read-only, idempotent, non-destructive operation, the description contributes nothing about return behavior, error conditions, or any side effects.

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?

At seven words, the description is concise, but it is under-specified rather than efficiently informative. It merely repeats the tool's name/title and fails to use the available space to add helpful context.

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 tool with no output schema and four parameters, the description is far too thin. It leaves the agent without guidance on the return shape, the meaning of redirect_posted, or how output_mode affects the result, making it insufficient for confident invocation.

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 description does not explain any parameters. The schema has descriptions for 'fields' and 'output_mode', but 'transaction_id' and especially 'redirect_posted' are left unexplained, and with 50% schema coverage the description needed to compensate for these gaps.

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 'Get transaction.' is essentially a verbatim restatement of the title 'Get Transaction' and the tool name. It identifies the resource and action, but it is a tautology and gives no distinguishing detail against sibling tools like transactions_get_transaction_splits or transactions_list_transactions.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no context about how it differs from the many other transaction-related tools. An agent must infer usage entirely from the name and schema.

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