Frontier-Compute/zcash-mcp

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

With no annotations provided, the description compensates by disclosing the return structure (root hash, unanchored leaves, anchor recommendation) since no output schema exists. However, it omits auth requirements or rate limiting context.

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?

Single sentence with zero waste: front-loaded action ('Get current ZAP1 Merkle tree state') followed by colon-delimited return value specification. Every word earns its place.

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 no output schema exists, the description adequately documents return values. For a zero-parameter read operation, this is sufficiently complete, though explicit read-only assurance would strengthen it given lack of annotations.

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 input schema has zero parameters, meeting the baseline score of 4. No parameter documentation is required or present.

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 verb 'Get' and resource 'ZAP1 Merkle tree state', and explicitly scopes it to 'current' state, clearly distinguishing it from sibling get_anchor_history.

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?

While the description implies usage through the 'current' qualifier (distinguishing from historical data), it lacks explicit when-to-use guidance or comparison to alternatives like get_anchor_history.

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