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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds that it refuses buy/sell/write actions, reinforcing the read-only nature, and mentions 'their data comes back as it is,' hinting at no transformation. However, it doesn't describe what output format or actual data the tool returns, nor does it explain the 'transfer hook' or 'seat' mechanics sufficiently. No contradiction with annotations exists, but the added behavioral detail is thin.

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 description is rambling and poorly structured. It starts with a clear sentence but then veers into confusing parenthetical fragments like 'a transfer hook (issuer code — Singularity Agent's MCP server, a live seat on The Wall (hosted by them).' It contains extraneous content (the listing URL) and unclear references. The key message gets buried, and there's no front-loading of the most critical guidance. The overall length is excessive for what could be communicated in two concise sentences.

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 no parameter descriptions, the tool description must fully explain what the agent should expect when calling it. The description gives the purpose but fails to describe the nature of the return—what 'mechanisms' means, what a typical response looks like, or how the data is presented. It mentions 'their data comes back as it is,' which is vague and unhelpful. The transfer hook and 'seat' concepts are not explained, leaving the agent uncertain about the tool's actual outputs and behavior. This is incomplete for a tool with no schema to fall back on.

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 schema coverage is 100% (trivially, since the schema is just an empty object with additionalProperties allowed). With no parameters, the description doesn't need to elaborate on param meanings. The baseline score for 0 params is 4, and the description adds no ambiguities about parameters, so it remains adequate.

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 states a clear purpose: to find out what could stop you from selling a Solana token before buying it. It distinguishes itself from generic token scoring by saying it 'names the specific mechanisms rather than scoring the token,' which implies a focused inspection. Though the phrasing is muddled and includes unrelated details, the core verb-resource relationship is present and distinct from typical buy/sell actions.

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 explicit usage context: 'Before buying a Solana token, find out what could stop you selling it.' This tells the agent exactly when to invoke it (pre-purchase) and what it serves (exit risk assessment). It also notes that read-shaped tools only are available and that write operations refuse, which guides the agent not to attempt mutations. While it doesn't name specific sibling alternatives, the timing and purpose are clear.

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