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

No annotations are provided, so the description carries the full transparency burden. It names the metrics but does not disclose whether this is a read-only snapshot, what freshness or limitations apply, whether any auth or connection is needed, or what the output shape is. 'Free' adds minor context but not enough behavioral detail.

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?

One dense sentence with no wasted words; every listed metric adds meaningful signal. The leading 'Free:' is slightly off-mission but does not make the description bloated.

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 zero-input market meter with no output schema, the description provides enough context by listing the metrics the agent can expect. It does not describe output formatting or update cadence, but those are minor gaps given the tool's simplicity.

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?

The tool has zero parameters and 100% schema coverage, so input semantics are trivially complete and the description does not need to compensate. This matches the baseline for a no-parameter tool.

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 clearly identifies a market-wide pump.fun regime meter and enumerates its metrics (launch rate, mayhem share, buy/sell flow, fail share, migrations vs true graduations, rug flags). It lacks an explicit verb, but the 'meter' framing makes the purpose clear and distinguishes it from per-mint or per-wallet sibling tools.

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?

Usage is implied: use this to assess overall pump.fun market conditions rather than individual tokens or wallets. However, there is no explicit when-to-use guidance, exclusions, or mention of alternatives, so the agent must infer selection from the sibling tool names.

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