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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered; the description adds genuinely new context — billing/auth behavior (no caller key required) and a strict parameter-exclusivity rule. It also names the return shape (total/vote/non-vote, success vs fail), which annotations cannot convey.

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 in a deliberate order: what you get, what it costs/requires, how to call it. Every clause carries information the agent needs and 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 correctly spends its words describing the returned fields and their granularity (daily, split by vote/non-vote and success/fail). All three parameters and their interaction are covered, so only minor details (e.g., response volume for a 365-day range) are unaddressed.

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 3 is the baseline, but the description adds the cross-parameter constraint that range and from_date+to_date are mutually exclusive — a rule an agent could miss while reading each property in isolation. It does not restate the enum values or date format, correctly deferring to 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?

Opens with a specific resource and verb-of-effect: daily Solana network transaction counts, broken into total, vote, and non-vote with a success/fail split. That metric breakdown is exactly what separates it from siblings such as get_network_fees, get_network_slots, and get_network_compute_units, so an agent can pick it without opening any 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?

The 'Free tier — covered by Pipeworx's own Solscan key, no caller key needed' line tells the agent the cost/auth posture up front, and 'Pass range OR from_date+to_date, not both' states the mutually exclusive invocation modes. What's missing is an explicit statement of when to reach for this versus a sibling network metric, so it stops short of a 5.

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