github_reactions_delete_for_pull_request_comment

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

The description only says 'Delete', indicating a destructive action. No annotations are present, so the burden is on the description to disclose effects (e.g., irreversibility, permission requirements), but it does not.

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 very short and to the point, using only essential words. It is front-loaded with the verb and resource, but lacks structural elements like examples or additional context.

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 fails to provide complete context: no mention of authentication, prerequisites (e.g., reaction must exist), or return value (no output schema). For a tool with 4 required parameters and no annotations, this is insufficient.

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?

Although input schema coverage is 100%, the parameter descriptions are just the parameter names (e.g., 'owner', 'repo'). The tool description adds no additional meaning, leaving the agent with only the schema's minimal information.

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 action ('Delete') and the resource ('pull request comment reaction'), which matches the tool name. However, it does not elaborate on the scope or that it targets a specific reaction by ID, which is implied by the parameters.

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?

No guidelines on when to use this tool versus alternatives like creating or listing reactions. The description lacks context for when deletion is appropriate or when other tools should be preferred.

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