Wait For Transaction

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

The description discloses polling behavior and return of combined inspection payload. Annotations are minimal, so description carries burden. It does not mention error handling on timeout or failure, but otherwise transparent.

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?

Single sentence, front-loaded with key action ('poll...until...then return'). No wasted words.

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?

Description provides core purpose but omits details about what 'combined inspection payload' contains and error scenarios. Adequate for basic use, but could be more informative.

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 100%, so the schema fully documents parameters. The description adds no parameter-specific information beyond what is already in the schema.

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 the tool polls for transaction status until a target status (accepted or finalized) and returns the combined inspection payload. It is distinct from sibling tools like get_transaction_status which are single-shot queries.

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 when waiting for a transaction to reach a status, but does not explicitly contrast with alternatives like get_transaction_status or get_transaction_receipt, nor does it state when not to use it.

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