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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuinely new operational context: the tool is free tier, it runs on Pipeworx's own Solscan key so no caller key is required, and the vendor rejects mutually-exclusive params with a 400. That is useful beyond the structured fields.

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, front-loaded with the payload contents, then the auth/free-tier note, then the parameter constraint. Every sentence is informative, though the final XOR sentence partially duplicates the schema and could be trimmed.

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 compensates well by enumerating the returned metrics and stating the daily granularity. Combined with the schema's documented defaults and date handling, an agent has enough to call it correctly; only the response shape beyond the metric list is left implicit.

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 enum, the default of 30, the YYYYMMDD format, and the 400-rejection behavior are already documented in the schema. The description's XOR sentence restates rather than extends that, so baseline 3 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 names the resource (Solana DEX activity) and enumerates the exact metrics returned — trade count, distinct traders, USD volume, active DEX platforms — so an agent knows precisely what it gets. It lacks explicit differentiation from nearby siblings like get_ohlcv or get_network_transactions, which keeps it short of a 5.

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?

It gives one concrete usage rule — pass range OR from_date+to_date, not both — plus the note that it is free tier with no caller key needed. There is no guidance on when another sibling would be a better choice, so usage is implied rather than fully scoped.

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