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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds that it is 'Read-only on chain, but advances the session record,' which explains the side effect on the session and clarifies the scope of read-only behavior. This is a valuable disclosure beyond the annotations, and it does not contradict them.

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, dense sentence that front-loads the core action and scoping condition. Every word contributes to meaning, with no filler or repetition.

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 4-param tool with no output schema and no param descriptions, the description is insufficient. It lacks explanation of parameters, expected response, prerequisites (e.g., an existing session), and how it fits into the overall flow. The description does not provide enough for an agent to call the tool confidently without external knowledge.

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 0% for four required parameters. The description only hints at 'burn_signature' (via 'already-submitted burn') and 'session_id' (via 'session record'), but does not explain access_token or idempotency_key at all. It fails to compensate for the missing schema documentation, leaving agents to guess parameter meanings.

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 uses a specific verb ('Verify') and names precise resources ('Circle attestation', 'forwarded Base or Arbitrum USDC mint'), and scopes it to 'an already-submitted burn.' This distinguishes it from siblings like assetfare_verify_source_receipt or assetfare_observe_destination by focusing on the CCTP mint after a burn.

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?

It implies usage after a burn has been submitted ('for an already-submitted burn'), giving a clear precondition. However, it does not explicitly state when to prefer this over sibling tools (e.g., assetfare_observe_destination) or what alternatives exist, leaving some ambiguity.

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