cryptopunks-mcp-server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively communicates key behavioral traits: 'Pure computation, no wallet required' indicates this is a stateless calculation without authentication or side effects, and 'Used to prove... for on-chain settlement' clarifies the real-world application. However, it doesn't mention performance characteristics, error conditions, or what the proof output looks like.

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 perfectly concise with three sentences that each earn their place: first states the core functionality, second provides important behavioral context (computation-only), third gives usage context. No wasted words, and the most important information is front-loaded.

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 3-parameter computational tool with no annotations and no output schema, the description provides adequate but incomplete coverage. It explains the purpose and behavioral context well but doesn't describe the proof output format, error conditions, or performance characteristics. Given the computational nature and lack of output schema, more detail about what the tool returns would be helpful for 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 description coverage is 67% (2 of 3 parameters have descriptions). The description adds minimal parameter semantics beyond the schema - it mentions 'single punk' and 'set of punk indices' which aligns with target_punk_index and punk_indices parameters. However, it doesn't explain the expected_root parameter (which has no schema description) or provide additional context about parameter relationships or constraints beyond what's in the schema.

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's purpose with specific verbs ('Generate a Merkle proof') and resource ('for a single punk within a set of punk indices'). It distinguishes from siblings by specifying it's for single-punk proofs (vs. batch operations like generate_batch_proofs) and mentions the context of collection bids for on-chain settlement, which differentiates it from verification tools like verify_merkle_proof.

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 context about when to use this tool: 'Used to prove a specific punk is included in a collection bid for on-chain settlement.' It implies this is for proof generation rather than verification or root calculation (distinguishing from verify_merkle_proof and generate_merkle_root). However, it doesn't explicitly state when NOT to use it or name specific alternative tools for different scenarios.

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