verify_merkle_airdrop_leaf

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It discloses a cost (0.01 USDC on Base L2) and implies a payment via the paymentSignature parameter, but it does not state whether the operation is read-only, whether it mutates state, or what the response format is. The word 'Verifies' suggests a read operation, but this is not explicit, leaving ambiguity about side effects and success/failure behavior.

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 two sentences with the primary action front-loaded. The parenthetical cost note is useful and concise. No filler words or redundant details. It is appropriately sized for the tool's complexity and maintains clear structure.

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 tool has no output schema and the description does not explain what it returns (e.g., boolean validity, error messages). For a verification tool that also involves a micropayment, it is critical to describe the return behavior and the role of the payment signature. The description leaves these gaps, making it incomplete for an agent to invoke correctly without additional inference.

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% and both parameters are described generically, but the description adds meaning by specifying that the payload contains the recipient address, token claim amount, and proof array. This goes beyond the schema's generic 'Input parameters or JSON string payload' and helps an agent construct a valid payload. The paymentSignature parameter is not elaborated beyond schema, but the core payload semantics are clarified.

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 states the tool verifies a recipient address, token claim amount, and proof array against an immutable Merkle airdrop distribution contract root. This is a specific verb+resource combination that distinguishes it from sibling tools like generate_merkle_proof (which generates proofs) and verify_evm_signature (which verifies different cryptographic constructs). The mention of 'immutable contract root' further clarifies its domain.

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 implies its use case (verifying airdrop claims) but does not explicitly state when to use it versus alternatives or provide exclusion conditions. For example, it does not say 'Use this when you have a Merkle proof to validate an airdrop' or contrast with zero_knowledge_merkle_membership_proof. The parenthetical about cost hints at a payment requirement but does not guide tool selection.

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