Delete a comment

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds real non-obvious behavior beyond that: an authorization boundary limiting deletion to the token owner's own comments. It stops short of describing failure behavior when the ownership check fails or whether the action is reversible.

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?

Three short sentences, zero padding, with the core operation front-loaded and the ownership constraint immediately after it. Every sentence carries distinct information.

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 two-param deletion tool with no output schema and annotations carrying the destructive/idempotent profile, the definition is nearly complete: operation, auth constraint and intended workflow are all present. Only the error/denial path when attempting to delete someone else's comment is left unstated.

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 100% and the schema already documents both ids (including the pointer to weeek_get_task for commentId). The description only implies that one parameter is a task and the other a comment, adding no syntax or format detail beyond the structured fields, so baseline 3 applies.

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?

States a specific verb and resource ('Deletes a comment from a task') and scopes it to task comments, which cleanly separates it from the sibling weeek_add_comment and the get/update task tools. An agent can identify the operation without opening the schema.

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?

Gives an explicit when-not ('Only comments written by the token owner can be deleted, never other people's') and a concrete when ('fix your own comment: delete it and add a corrected one'), routing the agent to weeek_add_comment for the follow-up. Nothing about selection is left to inference.

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