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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds 'Free', which is genuinely useful cost context, but says nothing about latency, whether attestation may be pending, or rate limiting for a status-polling tool.

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?

A single sentence with the most decision-relevant fact ('Free') front-loaded, then the return content and the input identifier. No padding or redundancy.

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?

An output schema exists and annotations carry the safety profile, so the description does not need to enumerate return fields — and it usefully names the return content anyway. The one real gap is routing versus the overlapping cctp_status sibling.

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 coverage is 100% and both parameters are already documented in the schema, including the enum and the hash pattern. The description's note that the hash is 'returned by the bridge call' restates what the schema already says, adding no new syntax or format detail.

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 resource and scope — 'Circle attestation and mint state for a bridge, by its burn transaction hash' — so an agent knows it returns bridging progress. However it does not distinguish itself from the sibling cctp_status, which plausibly covers the same attestation territory.

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 'returned by the bridge call' implies this tool is called after a bridge/quote operation to track the result, which is useful implied context. But there is no explicit when-to-use, no mention of polling cadence, and no disambiguation from cctp_status.

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