Delete Comment

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

The description states 'This is destructive for that comment', which aligns with the 'destructiveHint: true' annotation and adds context that the destruction is limited to the specific comment. It adds value beyond the annotation by specifying the scope of destruction.

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 extremely concise with just two sentences, yet it covers the essential purpose, usage guidance, and behavioral note. No unnecessary words.

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 simple deletion tool with one parameter, no output schema, and clear annotations, the description covers the core purpose, alternative usage, and behavioral impact. It is fully adequate for an agent to understand and use 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?

The input schema already has a well-described 'id' parameter with 100% coverage. The tool description does not add any additional meaning or context about the parameter beyond what the schema provides, so a baseline score of 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 clearly states 'Delete an existing comment by id', which is a specific verb and resource. It also distinguishes itself from the sibling tool 'resolve_comment' by explaining the difference in intent.

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 explicitly tells when to use this tool (delete a comment) and when not to ('use resolve_comment when you only want to mark a thread resolved'). This provides clear guidance on alternatives.

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