delete_ticket_tool

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

With no annotations, the description carries the transparency burdeneds by mentioning that the operation is destructive, irreversible, and removes the ticket plus all its comments, and that a confirm flag is required. It does not mention permissions or side effects beyond comments, but the core behavioral warnings are present.

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?

Three concise sentences plus a two-line arg list. The destructive nature is front-loaded)Skip supplementary. The text is efficient with no filler.

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 action with no output schema, the description covers the critical information: what will be deleted, irreversibility, and the confirmation requirement. It doesn't specify response behavior, but that is unlikely to prevent correct 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 0%, so the description must explain the parameters. It does: ticket_id identifies the ticket to deletehola confirm must be explicitly true to proceed. This adds clear meaning not present in the schema.

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', a precise resource ('ticket'), and the full scope ('and all its comments'), making the tool's purpose unambiguous and distinct from sibling ticket tools.

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 clearly indicates when to use the tool (when a ticket must be permanently removed), but it does not explicitly discuss alternatives or conditions that would make another tool more appropriate. The context is clear but exclusions are not stated.

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