Delete issue note

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

Annotations already disclose destructiveHint=true and readOnlyHint=false, so the destructive nature is known. The description adds the word 'permanently' to emphasize irreversibility, which adds slight value. However, it does not mention potential consequences like deleting the entire discussion thread or whether the operation can fail if the note is already marked for deletion. Given the annotations already flag destructiveness, this is an adequate but not rich contribution.

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 description is a single sentence, front-loaded with the action verb 'permanently delete', and contains zero wasted words. It fully communicates the tool's purpose in under 10 words.

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 the tool is a simple deletion operation with three well-documented parameters and an output schema (which presumably describes the response), the description is reasonably complete. It covers the action and the resource type, and annotations provide the safety profile. A 4 is warranted because it doesn't mention possible failure modes (e.g., permission errors) or pagination/limit concerns, but those are less critical for a deletion operation.

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 description coverage is 67% (two of three params have descriptions). The description itself does not add parameter-specific detail beyond the schema, but the schema's 'project' desc explicitly explains 'GitLab project ID or full path' and 'issue_iid' is described. The description's the verb 'delete' implies the note_id targets the deletion, but no further semantics like the note_id format or how to find it. Since coverage is decent, this meets baseline requirements.

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 clearly states the action (permanently delete), the resource (GitLab issue comment), and the scope (issue note). It distinguishes from siblings like update_issue_note and delete_merge_request_note by specifying 'issue comment' and the permanent nature of deletion. A 4 is appropriate because it lacks explicit mention of the API endpoint or the exact type of note (whether it's a discussion note or a regular note).

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 does not provide explicit guidance on when to use this tool versus alternatives. Given the sibling context, the agent could infer that this is for issue notes specifically, but no explicit exclusions or alternatives are mentioned (e.g., 'use delete_merge_request_note for MR notes'). The 'permanently delete' wording implies the action is irreversible, but this is not elaborated as a caution.

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