github_repos_delete_commit_comment

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

No annotations are present, so the description must carry the full burden. The description only states 'Delete a commit comment', which implies a destructive action but provides no additional behavioral traits such as permanence, authentication requirements, or error handling. For a delete operation, more context is needed.

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 sentence of three words that efficiently conveys the tool's purpose. It is front-loaded and contains no extraneous information, earning a high score for conciseness.

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?

Given the tool's simplicity (three standard parameters, no output schema, no annotations), the description provides the core action. However, it lacks completeness regarding prerequisites, side effects, or error scenarios. The 100% schema coverage partially compensates, but the description should offer more behavioral context.

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 100% with each parameter having a description in the schema (e.g., 'owner', 'repo', 'comment_id'), but these descriptions are minimal. The tool description adds no extra meaning beyond the schema, so it meets the baseline of 3 per the guidelines.

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 'Delete a commit comment' clearly states the verb (delete) and the resource (commit comment). It distinguishes from sibling tools like github_repos_create_commit_comment, github_repos_get_commit_comment, and github_repos_update_commit_comment, making the tool's purpose unambiguous.

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 usage guidelines are provided. The description does not specify when to use this tool over alternatives, such as when to delete a comment versus update it. It also lacks prerequisites or context about permissions or irreversibility.

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