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

With no annotations, the description carries the full behavioral burden. It discloses a key requirement ('Requires API key') and the noun 'Get' implies a read-only operation, but it does not explicitly confirm no side effects, mention rate limits, or describe data freshness. It adds some useful context but not deep behavioral disclosure.

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?

A single well-structured sentence: front-loaded verb and resource, then the metric list, then the auth requirement. Every word earns its place, and there is no redundant restating of the title or tool name.

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?

This is a simple no-parameter read tool, so the description covers the core needs: what data is returned (delegations, revenue, utilization, APY) and that API key auth is required. It stops short of describing the output format or possible error conditions, but that is a minor gap given the tool's simplicity.

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 a 100% schema coverage rate, so the schema already fully defines the input contract. The description's metric list is relevant context but not needed for parameter understanding; the baseline for zero-parameter tools 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 uses a specific verb ('Get') with a clear resource ('comprehensive statistics for your energy/bandwidth pools') and enumerates concrete metrics: delegations, revenue, utilization, APY. This distinguishes it from sibling tools like get_balance or get_market_overview, though it does not explicitly name any sibling alternative.

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 phrase 'comprehensive statistics' implies this is the go-to overview tool for pool performance, but there is no explicit guidance on when to use it instead of related siblings like get_pool_delegations, get_earnings, or get_available_resources. No exclusions or alternative routing are provided.

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