Frontier-Compute/zcash-mcp

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

With no annotations, description carries full burden. It discloses the Merkle tree destination and return value (leaf hash), but omits mutation safety details like irreversibility, confirmation requirements, or idempotency that would help an agent understand blockchain write semantics.

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?

Three sentences with zero waste: action/purpose front-loaded, mechanism explained, return value specified. No redundant phrases or boilerplate.

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?

Compensates for missing output schema by specifying return value (leaf hash). Mentions the ZAP1 system context. Could improve by noting api_key authentication requirement or required field constraints beyond schema, but adequate for tool complexity.

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%, establishing baseline 3. Description adds semantic context by mapping 'lifecycle, governance, or agent' to the event_type parameter values, but does not explain relationships between conditional fields (e.g., when proposal_id vs action_type is required).

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?

Description uses specific verb 'Create' with resource 'ZAP1 attestation event' and platform 'Zcash'. The second sentence clarifies it writes 'lifecycle, governance, or agent event' to the Merkle tree, clearly distinguishing it from read-only siblings like get_events or get_anchor_status.

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?

Implies usage through event categories (lifecycle, governance, agent) but lacks explicit when-to-use guidance or comparison to siblings. Does not clarify when to use verify_proof vs this tool, or prerequisites for attestation.

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