log_issue

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

Mentions that the issue 'survives interruptions and session boundaries', implying persistence. No annotations provided, so description carries burden but omits details like idempotency, error handling, or side effects.

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?

Four succinct sentences with no fluff. First sentence states purpose, second gives urgent usage instruction, third and fourth provide rationale. Front-loaded and efficient.

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?

Covers purpose, output, and usage context well, but lacks parameter explanations and error/edge case information. With no annotations, the description could be more comprehensive for a simple tool.

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 0% and the description does not explain what 'summary' or 'location' mean. While the tool's purpose is clear, the param meanings are left entirely to the schema, missing an opportunity to add value.

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 clearly states 'Open a new issue' and 'Returns the issue ID', providing a specific verb and resource. It distinguishes from siblings like 'get_issue' and 'add_note' by focusing on bug/regression reporting.

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?

Explicitly commands immediate use upon encountering bugs/regressions and emphasizes logging before fixing code. Lacks explicit when-not-to-use instructions but gives clear conditional guidance.

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