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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds content-level behavior by disclosing what is returned, including the notable funding_streams/lockbox_streams, but does not mention auth, rate limits, or freshness. Good added context without contradicting annotations.

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?

Front-loads purpose, then clearly labels 'When to use', 'Do not use', and 'Returns' sections. Every sentence carries routing or content value, with no filler despite being multi-sentence.

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?

With no output schema, the description compensates by enumerating the returned fields (mempool, height, verification_progress, block_reward_zec, funding_streams[], lockbox_streams[], etc.). Purpose, usage, exclusions, and returns are all present, so an agent has everything to call it correctly.

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 takes zero parameters, so the baseline is 4. The empty schema needs no elaboration and the description correctly focuses on outputs rather than inventing parameter semantics.

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?

States a specific verb+resource (get Zcash network and node state) and enumerates the exact contents: mempool, node version, difficulty, hashrate, chain progress/disk, block subsidy, and funding streams. It explicitly differentiates from siblings by naming zec_get_pool_status and chain_status, so an agent can pick it without opening the schema.

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?

Provides explicit 'When to use' (macro questions like hashrate, node catch-up, subsidy/funding) and 'Do not use' conditions routing to zec_get_pool_status for pool supplies and zec_get_pool_status/chain_status for node sync state. Alternatives and their selecting conditions are fully spelled out.

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