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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, yet the description adds real substance: replacement semantics for title/body/labels and the fact that GitHub keeps no undo. It stops short of covering permissions or the effect of combining comment with state changes.

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 tight sentences, with the operation list front-loaded and the destructive warning immediately after. Every clause carries information an agent needs.

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 destructive mutation with no output schema, the description supplies the safety warning and the key alternative tool, which is the main gap annotations cannot fill. It leaves some multi-parameter interactions (comment + state, assignees semantics) unaddressed.

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 only 11% across 9 parameters, so the description must carry weight; it does clarify the labels-vs-add_labels distinction and the replace-not-merge behavior of title/body. However, it says nothing about assignees (replace or append?), comment, or how comment interacts with state/title changes.

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 enumerates concrete operations (comment, close/reopen via state, title/body change, labels, add_labels, assignees) on a specific resource (issue or pull request), so an agent can match intent to tool. Minor deduction because the enumeration is a run-on list rather than a clean statement of scope.

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?

It explicitly routes the agent to the read sibling ('read the issue first (gh_issues)') and distinguishes the two label modes by flagging that labels replaces while add_labels adds. No explicit when-not-to-use case beyond that, so not a 5.

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