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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real context by naming what is bundled into the response (article references and source relationships). It does not say what happens when the id does not exist (error vs. empty), which matters for a by-ID lookup with no output schema.

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?

One sentence, front-loaded with the verb and scope, with the returned contents appended. No filler or redundancy.

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 simple one-parameter read with no output schema, the description gives a rough picture of the return payload, which is the main gap it needs to fill. It omits the id contract and not-found behavior, leaving the agent to infer both from the schema pattern.

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 0% for the single `id` parameter, so the description needs to compensate and does not — it never mentions the id, its expected format, or where to source it. The only clue to the format is the pattern in the schema itself, which is structured data rather than description value.

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 ("Return") and resource ("one evidence-backed claim from The Punks Are Permanent"), plus the payload scope (article references and source relationships). The resource type alone distinguishes it from siblings get_citation, get_document, and search_site, though it never names them explicitly.

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?

There is no statement of when to use this over search_site or get_citation, and no note that the id must already be known (or how to obtain one). Usage is only implied by the singular "one claim" phrasing.

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