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

Beyond the annotations, the description discloses concrete behaviors: live network fetch, capped comment thread, failure on private repos, precedent retrieval from the index, and no comment posting. These details reinforce the readOnly, idempotent, and non-destructive traits without contradicting them.

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?

Five short declarative sentences, front-loaded with purpose and key behavior. Every sentence contributes value, though phrases like 'scaffold' and 'Precedent from the index' are slightly cryptic and could be clearer.

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 two-parameter, read-only tool with rich annotations, the description covers access constraints, failure modes, side-effect absence, and live-fetch behavior. It does not describe the exact return shape, but no output schema exists and the behavioral detail is adequate for an agent to invoke it correctly.

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 100%, with both ref and url already documented in the schema. The description adds behavioral context around public issues but does not add extra parameter-level guidance such as ref/url precedence, matching the baseline for high schema coverage.

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?

Description names the resource (public GitHub issue), the behavior (live-fetches title, body, and capped comment thread), and explicit boundaries (private repos fail, does not post comments). This clearly differentiates it from sibling tools like analyze_pr or assess_argument.

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 description provides useful context about when the tool applies (public issues) and exclusions (private repos), but it never explicitly states when to prefer this tool over alternatives such as analyze_pr or assess_argument. Usage is implied rather than directly routed.

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