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

Annotations cover the safety profile (idempotent, non-destructive, open-world), and the description adds real operational context: verification happens on Base, requires 3 confirmations, and may return a 'pending' state requiring a re-call. That pending/retry behavior is not inferable from the annotations.

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?

Three short sentences, front-loaded with the trigger action and followed by verification and retry guidance. No filler sentences.

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?

No output schema exists, and the description usefully warns about the possible 'pending' response. Auth handling is covered by the schema. For a 2-param confirmation tool this is nearly complete, though it could note whether failed verification errors or returns a status.

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%, so both tx_hash and profile_key are fully documented in the schema. The description adds only that the hash is a Base transaction, which is marginal value beyond what the schema already states.

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 (confirm) and resource (deposit) plus the exact input action: submit the transaction hash after sending USDC. It implicitly separates itself from the sibling anthill_deposit, which initiates rather than confirms.

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 context for when to call it ('After sending USDC') and an explicit retry condition for the 'pending' case. It does not name an alternative tool for edge cases, but the usage window is unambiguous.

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