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

With no annotations, the description carries the burden of behavioral disclosure. It clarifies the network scope (mainnet), the data category (six value pools), and the conceptual domain (shielded-pool state). However, it does not mention output shape, freshness, units, or any operational caveats.

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 front-loaded with the core purpose and then provides concise usage guidance. The parenthetical list of six pools is somewhat dense but directly helps an agent understand the exact scope.

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 zero-parameter info tool with no output schema, the description covers the key facts: network, data scope, and when to choose this tool over siblings. It falls just short of a 5 because it omits any indication of what the returned data structure looks like, though the supply listing implies the main content.

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 tool has zero parameters and the schema is empty, so there is nothing to document. Description-based parameter semantics are not needed; the baseline of 4 applies.

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 names a specific verb/resource ('Zcash mainnet info including the supply of all six value pools') and clearly identifies the subject as shielded-pool state. It also distinguishes itself from a related sibling (chain_status) by explicitly saying what it is not for.

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?

It explicitly states when to use this tool ('how much ZEC sits in the shielded/sapling/orchard pools') and when not to use it ('whether the ZEC node is synced'), routing the agent to chain_status(zec) as the alternative. This leaves no ambiguity about selection.

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