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

Discloses behavior the annotations cannot: a fixed $0.005 per-call cost, USDC on Solana via x402, and the exact MCP retry protocol (call unauthenticated, receive PaymentRequired, retry with _meta["x402/payment"]). That is genuinely load-bearing context. It does not explain what happens on payment failure or whether an unpaid call is billed, which keeps it below a 5.

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?

Purpose is front-loaded in the first clause, followed by pricing and protocol details. Dense but nearly every clause carries information; the HTTP-equivalent URL is marginal for an MCP caller but not harmful.

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?

There is no output schema, and the description never indicates the shape of the result (bare titles? titles plus URLs/descriptions? how limit interacts with the result). Combined with no sibling differentiation from wiki_answer, an agent knows how to pay but not exactly what it receives.

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 both parameters are already documented; the description only adds that q is resolved to a Wikipedia page before links are extracted, which is a modest semantic gain over 'Question or topic'. The limit parameter is not mentioned at all 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?

States a specific verb+resource: returns articles linked from a resolved Wikipedia page. An agent can tell it apart from wiki_answer by the 'linked from' vs 'answer' framing, though the description never names the sibling to make the distinction explicit.

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?

Usage is only implied: an agent infers this is the tool for link-graph expansion, but there is no statement of when to prefer it over wiki_answer or of any prerequisites for the 'resolved page' (e.g. what happens if the topic is ambiguous or has no page). The payment instructions are procedural guidance rather than selection guidance.

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