delete_comment

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

Annotations already declare readOnlyHint=false and destructiveHint=true, and the description aligns with these by describing a destructive delete operation. It adds meaningful behavioral context beyond the annotations by specifying the authorization model: owner-only for own comments, space-admin for any comment.

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 that front-loads the core operation ('Delete a comment') and then adds the essential permission constraints. There is no irrelevant detail or redundancy.

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 one-parameter delete operation, the description covers the purpose and the relevant permission rules. It does not mention whether deletion is permanent or recoverable, but the destructiveHint annotation already signals destructiveness. Overall, the definition is sufficiently complete for an agent to select and 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?

The description does not mention comment_id at all, and schema description coverage is 0%, so the description was expected to compensate. The parameter is simple and self-descriptive from its name and UUID format, which prevents a score of 1, but no additional meaning is provided beyond the schema.

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 a specific verb and resource: 'Delete a comment.' It also differentiates this from siblings like delete_page, create_comment, and update_comment by naming the comment as the target. The permission scoping further clarifies what this operation means.

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 provides clear context for when the tool is allowed: owners can delete their own comments, and space admins can delete any comment. It does not name alternative tools explicitly, but the deletion context is unambiguous, and the permission model helps an agent determine whether to attempt the call.

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