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

Annotations already declare readOnly, idempotent, non-destructive, non-open-world, so the safety profile is covered. The description adds two useful facts beyond that: the call is free and the quote includes pumpdata's 0.4% fee. It stops short of saying how fresh the quote is or whether it accounts for slippage/price impact on large sizes.

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?

Very short and front-loaded with "Free." and the core output definition before the use cases. The fragment style ("what tokens sell for", "or what tokens sell for") is slightly elliptical and can be parsed ambiguously on a first read, but nothing is wasted.

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 read-only quote tool with no output schema and fully documented parameters, the description covers the essentials: what is quoted, on which venue, with which fee, and when to call it. It leaves the shape of the response implicit and says nothing about quote staleness, which matters since the value is explicitly point-in-time ("now").

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 the baseline is 3; the description goes beyond it by implying the SOL vs tokens split is driven by side (buy uses sol, sell uses tokens) and that the fee is already reflected in the quoted amounts. It does not address the 0.001–100 SOL bounds or default values, which the schema covers anyway.

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 verb (quote) and resource (pump.fun coin buy/sell amounts in SOL/tokens), including where the quote comes from (bonding curve or PumpSwap) and that the 0.4% fee is baked in. This clearly separates it from coin_price (price lookup) and buy_coin (execution).

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?

Gives concrete trigger phrasing ("how many tokens does 0.5 SOL get", "what would I get selling") and a sequencing rule ("before buy_coin"), which is strong when-to-use guidance. It does not explicitly say when not to use it or point at coin_price as the alternative for a plain price check.

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