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

Annotations already cover read-only, idempotent, open-world, non-destructive, so the bar is lower. The description still adds real value: it is free to call, it reports attestation and destination-mint state, and it supplies the recovery path (receiveMessage with message + attestation) for stuck transfers. Minor gap: nothing about rate limits or how long attestation takes.

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?

Front-loads the cost and purpose before elaborating returns and recovery steps. The trailing chain enumeration is long but matches the enum and is genuinely useful for confirming coverage; it is the only mildly expendable part.

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, so return-value documentation is not required, yet the description still names the key outputs (attestation, mint status) and the remediation path. Combined with 100% schema coverage and full annotations, an agent has everything needed to call it correctly.

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 both parameters are already documented including the 'source chain, if known (faster)' hint and the txHash pattern. The description reinforces that txHash is the source-chain burn hash and lists supported chains, but adds no syntax or format semantics beyond the schema. 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?

States a specific verb and resource ('Status of ANY Circle CCTP v2 USDC transfer') keyed to a concrete identifier (burn transaction hash), and its scope claim 'not only Liquid's' immediately distinguishes it from Liquid-specific siblings like bridge_status. An agent can tell what it does without opening the schema.

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?

Gives clear usage context: tracking any CCTP transfer and diagnosing/finishing a stuck one via receiveMessage. However, it never explicitly names or excludes the sibling bridge_status, so the routing decision between the two must be inferred.

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