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

Beyond the annotations (readOnlyHint, idempotentHint, etc.), the description discloses the detection method (reading USDC MINTS and correlating with CCTP receives), the lookback window behavior (default 30, max 90 days), pricing, and auth requirements via x-credit-token header. This adds substantial behavioral context.

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 front-loaded with the core purpose and method, but it contains some boilerplate ('Not financial advice'), redundancy ('Required input: wallet' repeats the schema and earlier param line), and promotional phrasing ('real signal', 'no other Base tool surfaces'). It is dense but not as tight as it could be.

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?

The description covers the what, how, why, parameter rules, pricing, and authentication requirements. Since an output schema exists, the description does not need to explain return values. The only minor ambiguity is 'No wallet or API key required,' which is slightly confusing given that a wallet address is required, but not enough to reduce completeness.

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 the baseline is 3. The description adds meaningful parameter detail beyond the schema by specifying that wallet is required and days is optional with a default of 30 and max of 90, which is not present in the schema property 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 states a specific action and resource: 'Cross-chain inflow detection' that reads a wallet's recent USDC MINTS and correlates them with Circle CCTP receives to determine whether USDC is freshly bridged and from which source chain. It clearly differentiates this tool from the large sibling list by claiming 'no other Base tool surfaces' this signal.

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 gives clear context for when to use the tool, calling it 'a real signal for trading and liquidation agents.' However, it does not explicitly state when not to use it or name alternative tools, so it falls short of full exclusionary guidance.

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