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

With no annotations, the description carries the behavioral burden and does disclose two non-obvious traits: saved reports expire after 30 days and can be stale, so check_token should be re-run. It omits what happens for an expired/unknown id (error vs empty) and any permission requirements, so it is strong but not exhaustive.

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?

Three short sentences, no filler: what it fetches, how the id is obtained, retention window, and staleness caveat. The essential identification info is front-loaded.

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 one-parameter read tool with no annotations and no output schema, the description covers purpose, id sourcing, retention, and staleness guidance. It leaves out not-found/expired behavior, which is the main remaining gap.

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 0% and the schema only labels the field "Trace Id", so the description must compensate — and it does, explaining the id is the code at the end of a rugradar-dun.vercel.app/r/... link. That tells the agent exactly where to source the value, though no format/validation details are given.

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 specific verb and resource ("Fetch a saved RugRadar check") plus the addressing key (id from a /r/... link). It also implicitly distinguishes itself from check_token, which performs a fresh run. An agent can tell exactly what this returns without opening the schema.

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?

It states when results are trustworthy ("Saved checks last 30 days") and explicitly names the alternative and condition: "Re-run check_token before relying on an old one: tokens change fast." This is a concrete when-to-use/when-to-switch rule, not an inference.

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