Get transaction

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

The description adds 'full details' but otherwise the read-only, idempotent, non-destructive behavior is already declared by annotations. No contradiction, and the description does not need to repeat annotation-provided safety traits.

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, direct sentence with no filler. It immediately states the action and scope, making it easy to parse quickly.

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?

Given the low complexity, one well-documented parameter, rich annotations, and the presence of an output schema, the description is sufficient for an agent to select and invoke the tool correctly without additional return-value details.

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 fully describes the only parameter as 'Monarch transaction ID' with 100% schema description coverage. The description adds no additional parameter meaning, so 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?

The description uses a specific verb and resource: 'Get full details for one transaction.' It clearly distinguishes itself from the plural 'get_transactions' and other transaction-related siblings by emphasizing a single transaction and full details.

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 singular 'one transaction' provides clear contextual signal that this tool is for individual lookups, differentiating it from get_transactions. It does not explicitly mention alternatives, but the scope is evident from the description and naming.

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