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

Annotations only flag destructiveHint=true; the description supplies the non-obvious cascade rule that deleting a thread's first comment removes the whole thread, plus the caller-ownership restriction. Those are precisely the behavioral facts an agent cannot derive from the schema or annotations, and they directly alter invocation safety.

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?

Two short sentences, zero padding, with the cascade warning and confirmation instruction front-loaded where it will be read before the call is made.

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 destructive tool the safety behavior is well covered, and an output schema exists so return values need no explanation. The gap is parameter meaning: with both identifiers undocumented in the schema and absent from the description, an agent cannot tell what projectUid contributes.

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 0% for two required parameters, so the description carries the full explanatory burden and does not meet it — neither commentUid nor projectUid is mentioned, and their relationship (comment scoped within a project) is never stated.

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 ("Delete one of the caller's own comments") and adds an ownership scope, which implicitly separates it from update_comment and get_comments. It never names a sibling explicitly, so an agent must infer the routing, but the action is 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?

The description gives one concrete operational guideline — ask for explicit confirmation before deleting a thread's first comment — and the ownership restriction implies what is out of scope. It does not say when to prefer this over update_comment or how to obtain the commentUid, leaving the broader usage decision implicit.

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