delete_merge_request_note

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

No annotations exist, so the description carries the full burden, but it discloses nothing beyond the destructiveness implied by the verb "delete." It does not state that the operation is irreversible, that permissions are required (e.g., only the note author can delete), or what happens on failure (404/403); the word "existing" is the only behavioral hint, implying deletion of a missing note fails.

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 sentence is tight, grammatical, and front-loaded with the verb, with zero filler, so the structure itself is fine. However, the brevity is under-specification rather than disciplined editing — the description is too short to handle the sibling-disambiguation task it faces.

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, 3-parameter operation with no annotations and no output schema, too much essential context is missing: which sibling to use for threaded notes, which parameters are actually required, and what success/failure looks like. The schema at least documents parameter names, which keeps this above a 1, but the description is far from adequate for safe invocation.

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%, so each parameter is already documented and the baseline is 3; the description adds no parameter-level meaning. It also does not compensate for the schema marking all three parameters as optional even though a delete call needs all of them, nor does it clarify the ambiguous phrase "ID of a thread note" used for note_id.

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 "Delete an existing merge request note" is effectively the tool name expanded into a sentence; it adds only the qualifier "existing" and no differentiating detail. It fails the most important test here: it does not distinguish this tool from the near-twin sibling delete_merge_request_discussion_note, whose plain-language meaning is nearly identical.

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?

There is no guidance on when to use this tool versus its alternatives. It never mentions that a note inside a discussion thread should go through delete_merge_request_discussion_note, nor does it contrast with delete_draft_note for unpublished notes, and it omits preconditions such as author-only deletion. With a sibling this similar, the absence of selection criteria is a serious gap.

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