add_issue_comment

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

With no annotations, the description carries the full burden of behavioral disclosure. It does reveal a key trait: the action is queued rather than executed immediately, and is subject to human approval. However, it omits other potentially important details such as required permissions, side effects, or what happens after approval, leaving a moderate transparency gap.

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 a single, well-structured sentence that front-loads the core purpose and immediately notes the approval-queue behavior. Every word earns its place, with no unnecessary detail or repetition.

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?

The description covers the tool's main purpose and its most distinctive behavior (queuing for approval), and an output schema exists to document return values. However, given that parameter descriptions are entirely absent and usage guidance is only implicit, the description leaves some gaps for an agent to fully invoke the tool 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 0%, and the description does not mention any parameters. The parameter names (owner, repo, issue_number, body) are self-explanatory, but the tool description adds no explicit meaning or usage guidance, so it fails to compensate for the lack of schema descriptions.

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 'Request an issue comment', which is a specific verb+resource combination. It also distinguishes itself from siblings like create_issue or add_labels by noting it 'queues exact action for human approval', indicating a different execution model.

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 implies this tool should be used when a comment needs to be queued for human approval, but it does not explicitly mention alternatives or when not to use it. The context is clear enough for basic selection, but no direct exclusions or sibling comparisons are given.

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