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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds genuinely new context: this is a free tier backed by Pipeworx's own Solscan key, so no caller credentials are needed. It does not mention rate limits or result volume, which is the only remaining gap.

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?

Three short sentences, metric first, auth second, parameter rule last. Every sentence carries information an agent needs; nothing is repeated from the schema verbatim.

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 tells the agent the data is a daily count, which is enough to interpret results. It could still be clearer about output shape (one row per day vs. an aggregate) and about behavior when no parameters are supplied.

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 coverage is 100%, so the baseline is 3; the description earns above that by stating the mutual exclusivity of the two date modes as a caller-side rule, complementing the schema's note that range is ignored (and that other range values get a 400).

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 metric and resource: 'Daily count of Solana blocks (slots) produced.' That is clearly distinct from sibling network tools like get_network_fees or get_network_compute_units, though the description never explicitly contrasts itself with 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?

'Pass range OR from_date+to_date, not both' gives an explicit calling rule that prevents a common failure mode. It falls short of a 5 because it doesn't say when to prefer this over sibling network metrics or note that all parameters are optional.

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