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

With no annotations, the description relies on the verb 'Get' to indicate a read-only operation, which is a clear behavioral signal. It also adds nuance by stating 'output if delivered', implying the output may be absent. However, it does not discuss error behavior or potential side effects, leaving some gaps.

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 sentence with no redundant phrases, front-loads the action ('Get'), and efficiently lists the key return fields. Every word earns its place.

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 simple getter with one parameter and no output schema, the description adequately outlines what is returned (status, parties, pricing, output if delivered). It could be slightly more explicit about error responses, but it is sufficient for the tool's complexity.

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 transaction_id is already fully described in the schema as a UUID. The description adds no additional semantics beyond confirming the target is a transaction, so it meets the baseline without augmenting schema coverage.

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 specifies the tool's function: retrieving the current state of a transaction, including concrete data fields (status, parties, pricing, output if delivered). This distinct verb+resource combination differentiates it from sibling tools like ae_create_transaction or ae_negotiate.

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 usage for fetching transaction state but provides no explicit guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or context such as 'after creating a transaction'.

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