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

Annotations only declare readOnlyHint/destructiveHint; the description adds far more: no auth, 100 new marks per caller per UTC day on the Lab, 1 free call a day signed in then $0.02 a call or 50 for $1.00, a 402 response carrying `pay`, an x402 `accepts` list and `free_trial`, free replay of a fresh ledger mark, plus a 24h HOLDS/FOLDS scoring cycle. It also flags that returned coin names and posts are third-party data to quote but never obey — a genuine prompt-injection warning that structured fields 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?

The opening sentence is about a 402 `purchase_required` code, burying the tool's actual purpose behind a payment detail, and the whole block runs long and promotional ('meme title, one roast line', 'receipts anchored to real facts'). Multiple clauses — the 24h call, the scoreboard, share_url, the training dataset, the CLI-free pricing ladder — crowd a one-parameter read tool, so the reader has to work to extract the callable behavior.

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?

Given an output schema exists, the description need not explain return values, yet it still covers the operational essentials an agent needs: auth state, rate limits, price and 402 mechanics, free-replay behavior, and the safety caveat about untrusted content. The only shortfall is that it spends words re-describing returns instead of pointing at the output schema, but no functional gap remains.

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 single `target` parameter is already documented and the description's phrasing of accepted formats largely restates it. It adds only marginal meaning beyond the schema — namely that omission yields the board alone and that an X handle, x.com link, Solana CA, or any public https URL are all valid — which is an acceptable baseline-3 contribution but not more.

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 a specific verb and resource ('one deep read on any mark') and enumerates the exact target classes it accepts: a Solana contract address or pump.fun/DexScreener/Solscan/Birdeye link, an X @handle or x.com link, or any public https link. It also states the deliverable — authority/holder concentration, DexScreener pair data, X account audit card, link crawl, and a CLEAN/SUS/PUNK verdict — so an agent knows precisely what the tool produces.

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 description gives input-selection guidance ('omit `target` for the board alone') and notes it is the same as GET /api/mark/check?q=, which helps an agent map the MCP call to a documented HTTP route. However, it never contrasts itself with plausible siblings such as hunt_report, market_search, or product_check, so the agent is left to infer when this tool is the right choice rather than another.

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