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

No annotations exist, so the description carries the full burden. The verb 'Retrieve' implies a read-only lookup and the enumeration of returned content adds real value, but there is no disclosure of permissions, lookup failure behavior, or what 'verified' means operationally.

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?

A single front-loaded sentence with the resource and identifier up front, followed by the content enumeration. Minor adjective padding ('in-depth', 'all verified') slightly inflates it but nothing is wasted.

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, the description must speak to return values, and it does enumerate content types but gives no sense of structure, size, or ordering. For a read tool with one parameter this is adequate but leaves the agent guessing at the response shape.

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%, and the description's 'by slug or URL' merely restates what the schema already documents with an example. Baseline 3 is appropriate since the schema does all the parameter work.

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?

A specific verb ('Retrieve') plus a specific resource ('a specific problem') with an enumeration of what is returned (consensus details, workarounds, quotes, venue distribution). This clearly separates it from the search-oriented sibling, though it never names the sibling 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?

The phrase 'by slug or URL' implies the tool is the detail-fetch step for a known problem, which indirectly distinguishes it from search_problems. However, no explicit when-to-use/when-not guidance or alternative routing is given.

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