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

With no annotations, the description carries full burden. It discloses that verification is chain-only, never depends on trust signals, and withTrust adds advisory trust without affecting the paid verdict. It implies no side effects (read-only). Could be more explicit about data mutation or side effects, but adequate.

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 highly concise: two sentences with zero waste. It front-loads the main purpose and immediately clarifies key behavioral traits. Every sentence adds value.

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?

Given the tool's complexity (4 parameters, no output schema, 28 siblings), the description covers the main function and key constraints. However, it does not describe the return format or how the 'paid verdict' is communicated, which is a completeness gap.

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 50% (withTrust and lookbackBlocks have descriptions; to and amountMicro lack). The description adds meaning by explaining 'field-for-field' verification and the default for lookbackBlocks. However, it does not explicitly define 'to' and 'amountMicro' beyond context, so it partially compensates for missing schema descriptions.

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 clearly identifies the tool's function: watch Base for USDC transfer and verify it field-for-field. It uses specific verb-resource pairing ('Watch Base for the USDC transfer paying a charge and verify it') and distinguishes from siblings by focusing on chain-only payment verification without trust signals.

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 description provides clear usage context: when to use (to verify USDC payment), what constitutes 'not paid' (wrong chain/token/recipient/underpay/unconfirmed), and optional trust addition. It lacks explicit when-not-to-use or alternative tool guidance, but the context is sufficient for an agent.

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