report_issue

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

No annotations are provided, so the description carries the full burden. It discloses that the tool is non-blocking, logs and continues the task, and that silence is the failure mode. It does not detail side effects like persistent storage, but for a logging tool this is sufficient.

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?

The description is front-loaded with a clear purpose, followed by a well-formatted bullet list of when to use, a behavioral note, and parameter definitions. Every sentence is necessary and efficiently conveys information without 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 tool's purpose (logging issues), the description covers all essential aspects: usage triggers, behavior, parameter constraints, and output expectations (none). It is fully self-contained and eliminates the need for additional clarifications.

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?

With 0% schema description coverage, the description compensates fully by defining each parameter: description (max 200 chars), severity (with options low/medium/high), section (max 80 chars), and mode (with enum values). It also indicates defaults, making the schema's bare types actionable.

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 clearly states the tool is for reporting bugs, confusion, bad documentation, or improvement ideas. It uses a specific verb 'report' and resource 'issue', and distinguishes use cases via bullet points, making its purpose unmistakable even without sibling context.

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 explicitly lists when to call the tool (e.g., when guessing, missing tool, unclear docs, ambiguous instructions) and provides guidance on its non-blocking nature, lack of expected response, and absence of penalty. This leaves no ambiguity about appropriate usage.

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