zero_knowledge_merkle_membership_proof

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

With no annotations, the description carries the full burden. It discloses the cost (0.050 USDC on Base L2) and the privacy property (without revealing identity), but it does not state whether the operation is read-only, has side effects, requires network access, or what errors may occur. It partially covers behavioral traits but leaves significant gaps.

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 sentence followed by a parenthetical cost note. It is front-loaded with the core function and includes the cost as a secondary detail. There is no fluff, making it highly concise and efficient.

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 cryptographic tool of this complexity, the description is minimal. It does not explain what the payload should contain (e.g., merkle root, leaf, proof), what the output structure is (no output schema), or any constraints. The absence of these details leaves an agent uncertain about how to invoke the tool correctly. The cost note adds context but does not compensate for missing input/output specifics.

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?

The schema already describes both parameters fully (payload and paymentSignature), achieving 100% coverage. The description adds no additional meaning about the parameters, so the baseline score of 3 applies. It does not clarify expected formats or relationships beyond what the schema 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?

The description clearly states a specific action ('Generates and verifies') on a specific resource ('Poseidon hash-based Merkle tree membership proofs') and includes the purpose ('private zero-knowledge credential verification without revealing identity'). It distinguishes itself from generic Merkle proof tools by emphasizing the zero-knowledge and Poseidon hash specifics, but it does not explicitly name alternative siblings like generate_merkle_proof or verify_merkle_airdrop_leaf, so it misses a clear differentiation.

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 no guidance on when to use this tool versus its siblings. It does not mention alternatives, conditions, or exclusions. An agent must infer that this is for zero-knowledge credential verification, but there is no explicit routing information.

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