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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's added value is the auth/cost disclosure (no caller key, free tier) and the vendor's 400 rejection behavior. It does not mention rate limits or whether the daily series is contiguous, but the key operational facts are disclosed.

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 tight sentences: what you get, what it costs/auth-wise, how to parameterize. Nothing redundant and the payload description is front-loaded where an agent will read it first.

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 three-optional-parameter read tool with no output schema, the description names the returned fields, the units (SOL and USD), the auth posture, and the parameter exclusivity rule. An agent can call this correctly from the description alone.

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% and the schema descriptions already state the range enum, default 30, and that range is ignored with a 400 when from_date/to_date are supplied. The description's "Pass range OR from_date+to_date, not both" restates that constraint compactly but adds no format or semantic detail beyond the schema.

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?

Names a specific verb and resource and enumerates exactly what the response contains: daily base fee, priority fee, each in SOL and USD, plus their total. That distinguishes it from siblings like get_network_compute_units or get_network_slots even without naming 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 "Free tier — covered by Pipeworx's own Solscan key, no caller key needed" line tells the agent when this is cheap to call, and the closing rule constrains parameterization. It gives clear context but names no alternative sibling and no when-not-to-use case.

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