get_transaction

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

No annotations are provided, so the description carries full burden. It lists all fields returned, which adds clarity about the output. The phrase 'Get details' implicitly indicates a read-only, non-destructive operation, but an explicit statement about safety (e.g., 'This is a safe read operation') is missing.

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 well-structured with bullet points, but it is verbose, listing all return fields. Since an output schema exists, this redundancy reduces conciseness. The opening sentence is good, but the detailed list could be omitted.

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 (1 parameter, output schema available). The description covers the parameter, explains what is returned (though redundant), and provides context. It is complete for this tool, but could explicitly state it is a read-only operation.

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 input schema has 0% description coverage, but the description explicitly documents the parameter as 'transaction_id: ID of the transaction to retrieve,' providing meaning beyond the schema's type-only definition. With a single parameter, this is clear and sufficient.

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 it gets details of a specific transaction, using a specific verb+resource ('Get details about a specific transaction'). It distinguishes from the sibling tool 'get_transactions' which retrieves multiple 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?

The description implies use for a single transaction via 'specific transaction' and mentions the transaction_id parameter, but does not explicitly state when to use this tool versus alternatives like get_transactions, nor does it mention any prerequisites or exclusions.

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