Frontier-Compute/zcash-mcp

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

With no annotations provided, the description carries the full burden. It successfully clarifies that the tool generates a payment URI rather than actually transferring funds (critical given the 'send_shielded' name), but fails to disclose return format, error handling behavior, or whether network connectivity is required.

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 consists of two efficient sentences with zero redundancy. It is front-loaded with the core action (Generate URI) followed by implementation details (encodes specific fields), making it easy to scan.

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?

Given 100% schema coverage and simple parameter types, the description adequately covers inputs. However, with no output schema provided, the description should ideally specify what the tool returns (the URI string). It leaves gaps regarding error states and validation behavior.

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%, establishing a baseline of 3. The description adds minimal semantic value by noting parameters are 'encoded into a scannable URI', but does not elaborate on parameter interactions, format constraints beyond the schema, or the purpose of the 'label' parameter which is omitted from the description text.

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 uses specific verbs ('Generate', 'Encodes') and clearly identifies the resource as a 'zcash: payment URI for shielded ZEC'. It distinguishes from siblings (which query status, decode memos, or verify proofs) by specifying URI generation functionality.

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 alternatives, nor does it mention prerequisites or exclusions. While the functionality is unique among siblings (no other tool generates payment URIs), explicit contextual guidance is absent.

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