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

With no annotations, the description carries the behavioral burden. It usefully discloses that comment bodies are returned verbatim, a judgment_prompt is included, and the host (not the tool) performs classification. This goes beyond a simple fetch description, though it does not address rate limits or failure behavior.

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?

Two sentences, front-loaded with the core purpose, followed by a concise behavioral note about the returned comment bodies and judgment_prompt. Every sentence earns its place with no 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?

Given the output schema exists and the schema covers most parameters, the description provides enough context for a capable agent: what the tool fetches, what it returns, and who performs classification. It is missing explicit usage boundaries versus siblings, but the core invocation context is complete.

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?

The description does not add parameter-level meaning beyond the schema. The schema already documents entity, problem, issue_limit, and comment_limit; since/until are self-explanatory by name. With 67% schema coverage, the description does not need to compensate heavily, but it also adds no parameter detail.

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 ('Fetch'), a specific resource ('raw GitHub issue threads'), and the exact purpose ('for the host to judge workarounds / fixes'). This clearly differentiates it from sibling search/discussion tools by focusing on GitHub issue threads and workaround candidacy.

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 purpose implies when to use it — when raw GitHub issue threads are needed for workaround vs official-fix judgment — but it does not explicitly state when not to use it or name alternative tools. Usage context is clear but left to inference.

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