manage_comment

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

With no annotations, the description carries full burden and it partially delivers: it discloses the Server-only restriction on to_task/to_comment and hints that version makes writes faster. However, it omits whether delete is reversible, what permissions are required, and what happens to concurrent edits beyond the schema note. Adequate but incomplete for a mutation tool.

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 compact sentences that front-load the action set before the constraint and version note. No obvious filler, though the parenthetical Server annotations are slightly terse.

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 multi-action mutation tool with no output schema, the description covers the operation set and the version/Server constraints but leaves return values, error behavior, and permission requirements unaddressed. It is minimally sufficient rather than 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?

Schema coverage is 71%, so most parameters are self-documented. The description adds the source of version ('from get_pull_request output'), which the schema does not state, but contributes nothing else beyond the schema for text/action/workspace. Baseline 3 is appropriate.

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 the specific operations (edit, delete, resolve, reopen, convert) applied to a concrete resource (PR comment or task). This cleanly separates it from siblings like add_comment (which creates) and the update_pull_request family. An agent can identify the tool's role without opening the schema.

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 action list implies when to use each operation, and the '(Server-only)' note scopes to_task/to_comment, but there is no explicit guidance on when to choose this over add_comment or how a caller decides between action values. Usage is inferable rather than stated.

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