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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered without description help. The description adds no further behavioral detail such as result ordering guarantees, snapshot vs. live semantics, or pagination, which matters given idempotentHint=false on a read tool. Adequate but thin beyond the annotations.

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?

Two sentences, purpose front-loaded, routing information second, zero filler. Every clause earns its place.

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 and a single self-evident integer parameter, the description covers what an agent needs to decide to call this tool. The only shortfall is that the limit parameter is unexplained, but that is a minor gap for a low-complexity read tool.

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 0% for the single 'limit' parameter, so the description has to carry the burden and does not mention it at all. It never states what limit controls, the 1-50 bounds, or the default of 10, leaving the agent to guess from the parameter name.

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 resource (pump.fun tokens) plus the ranking criterion (market cap), which is exactly what distinguishes it from the other token-listing siblings. An agent can tell it apart from get_new_tokens and get_graduated_tokens without opening either 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?

Explicitly names the condition for this tool ('scan the largest coins on pump.fun right now') and routes to two named alternatives for the adjacent cases (fresh launches, graduated coins). This is a clean when/when-not/alternatives statement with nothing left to inference.

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