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

Annotations already declare readOnly, idempotent, and non-destructive behavior, lowering the burden on the description. The description adds useful context that the tool is free, that results include prices and payment instructions, and that it is meant as an entry point. No annotation contradiction.

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 two sentences with no filler. The first defines what the tool returns in a compact list of data categories, and the second gives a direct usage directive. Key context, including cost and ordering, is packed efficiently.

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-parameter list tool with rich annotations, the description covers purpose, scope, cost, and invocation ordering. It does not describe the output structure, but with no output schema and simple list semantics, this is a minor gap rather than a blocking omission.

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?

There are zero parameters and schema coverage is 100%, so there is no parameter ambiguity for the description to resolve. This matches the baseline for a no-parameter tool; nothing more is needed in the description.

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 title and description identify a clear verb (list) and resource (data endpoints), then spell out the scope: 'live Solana token, wallet, launch and market data' plus pricing/payment details. This distinguishes it from sibling tools like get_endpoint or search_endpoints by presenting itself as the broad catalog of everything available.

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 explicitly tells the agent when to use it: 'call this first to see what exists.' This is actionable and prevents agents from guessing which endpoint to start with. It does not name sibling alternatives or state when not to use it, but the first-call directive provides strong usage guidance.

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