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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is covered by structured data. The description adds two things annotations cannot: the cascading deletion of replies when the note starts a thread, and the authorization constraint. It stops short of stating irreversibility or the response shape.

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 compact sentences, both earning their place: the first defines scope and cascade behavior, the second defines who is permitted. Nothing is redundant and the core action leads the sentence.

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 with an output schema present and destructive annotations declared, the description supplies the two non-obvious facts an agent needs — cascading reply removal and the permission requirement. Only irreversibility/error conditions are left unstated, which is a minor gap.

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?

There is a single required parameter whose schema description is fully covered (100%), so the schema carries the load and baseline is 3. The description's use of 'note' where the schema says 'comment_id' is a mild terminology mismatch rather than added semantic guidance.

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 ('Delete') and resource ('a note'), and the parenthetical clarifies that deleting a thread-starting note also removes its replies. It is distinguishable from resolve_comment or list_comments by the outright removal, though it never names those siblings explicitly.

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?

It gives a real precondition — only the note's author or the presentation owner may perform the deletion — which is genuine usage context. It does not, however, say when to prefer this over the sibling resolve_comment, leaving that choice to inference.

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