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

No annotations are provided, so the description carries the full behavioral burden. 'Check' implies a read-only operation, but the description never addresses the critical behaviors for a tx-confirmation tool: what happens if the tx is still pending or unknown, whether it waits/polls or returns immediately, whether it errors or returns empty, or which chain it inspects.

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?

One sentence, zero filler, with the action and the return value both front-loaded. Nothing could be removed without losing information.

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 description usefully compensates for the missing output schema by stating the return is token ids, and the tool is structurally simple (one required string). But for a confirmation tool the pending/failed/unknown-tx outcomes are the main thing an agent needs and they are absent.

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 txHash parameter has 0% schema description coverage, so the description must compensate. It does add real meaning — the hash must belong to a *sent mint* transaction — but it gives no format expectations (0x-prefixed, length) or what happens with a non-mint or malformed hash.

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?

States a specific verb ('check') plus the resource ('a sent mint tx hash') and even the return value ('the token ids it minted'). This clearly separates it from the sibling 'mint' (which sends the tx) and 'quote_mint' (which prices it), though it never names those siblings explicitly.

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 phrase 'a sent mint tx hash' implies this is the post-broadcast verification step in a mint flow, which is useful implied sequencing. However there is no explicit when-to-use/when-not statement, no mention of what to do if the mint has not been broadcast, and no named alternative for re-requesting a mint.

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