Delete note

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. However, the description adds no behavioral context beyond those annotations—it does not say what gets removed, whether replies/threads are affected, or what permissions are required.

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 single sentence is concise but not appropriately sized for a five-parameter destructive tool; this is under-specification rather than effective brevity. There is no front-loaded context because there is essentially no content beyond the title.

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?

Given five undocumented parameters, no output schema, and destructive semantics, the description is completely inadequate. It provides none of the context an agent needs to invoke this tool safely or 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 schema has five parameters with 0% description coverage, and the description mentions none of them. It provides no meaning for note_id, project_id, issue_iid, body, or data, leaving the agent with no guidance on how to target the correct note.

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 a note' merely restates the tool name and title, which is the definition of tautology. It gives no scope (project/issue/merge request note), no differentiation from sibling delete tools, and no indication of what resource hierarchy the note belongs to.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as gitlab_update_note or gitlab_get_note. An agent must infer entirely from the name that this is a deletion operation and cannot tell from the description when deletion is appropriate versus other note operations.

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