delete_ticket_note

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

Annotations are absent, so the description must disclose behavioral traits. It only states the delete action but does not mention irreversibility, permissions, validation of the note's association with the ticket, or side effects. This is a significant gap for a mutation tool.

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 appropriately concise and front-loaded, with the action stated first and parameters listed clearly. Every word earns its place; there is no unnecessary content.

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 simple two-parameter delete tool, the description is minimally complete. It omits information about side effects, return values, and validation, but the output schema (if available) would cover returns, and the low complexity reduces the burden. Still, some behavioral context is missing.

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 description adds basic semantic meaning for both parameters, clarifying that conversation_id is the note ID. However, the schema titles already convey 'Ticket Id' and 'Conversation Id', and the description does not explain relationships or constraints. It compensates modestly for 0% schema coverage but lacks depth.

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 ('Delete') and the resource ('a note from a ticket'). It distinguishes itself from sibling delete_ticket (which deletes entire tickets) and add_ticket_note (which adds notes), providing a specific and unambiguous purpose.

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?

No guidance is provided on when to use this tool vs alternatives, nor any context about prerequisites or exclusions. The description only says what it does, not when to choose it over related tools like list_ticket_conversations or reply_to_ticket.

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