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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior. The description adds useful behavioral context beyond that: the call is free-tier, requires no caller key because Pipeworx supplies its own Solscan key, and invalid range values are rejected by the vendor with a 400.

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 three short, front-loaded sentences with no filler. It states the purpose first, then auth/cost context, then the key parameter constraint.

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 simple three-parameter read-only network metric with rich annotations and full schema coverage, the description covers the essentials: what it returns conceptually, auth/cost context, and parameter-mode constraints. It does not describe response shape, but the tool is straightforward enough that this is a minor gap.

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%, so the parameter meanings, enum values, date formats, and range-vs-date behavior are already well documented in the schema. The description reinforces the mutual exclusivity of range and from_date/to_date, but adds little beyond what the schema already provides.

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 states a specific metric and scope: daily total compute units consumed across the Solana network. It is clearly distinct from sibling network metrics such as fees, slots, stake, and transactions, but it does not explicitly differentiate itself from them.

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 gives parameter-mode guidance ('Pass range OR from_date+to_date, not both') and notes the free-tier/no-caller-key context. However, it does not explicitly say when to use this tool instead of sibling network metric tools or when not to use it.

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