delete_ticket

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

No annotations are provided, so the description carries the full burden. It discloses that this is a soft delete ('Trash'), a key behavioral trait distinguishing it from a permanent delete. However, it does not address permissions, side effects on related entities, or recoverability beyond the soft-delete implication.

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 two sentences long and front-loaded with the action and its behavior. The Args section is minimal and directly relevant; no redundant or filler content exists.

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's low complexity (single required param, output schema present), the description covers the essential action and parameter. It lacks contextual information such as when to use soft delete vs. permanent deletion, but the core is complete for a simple delete operation. The presence of an output schema covers return values.

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 a single parameter with no property description (0% coverage). The description compensates by including an Args section that defines ticket_id as 'The ticket ID to delete,' adding meaningful semantics beyond the schema's bare type of integer.

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 uses the specific verb 'Trash' and explicitly clarifies 'soft delete', clearly distinguishing this from sibling tools like delete_ticket_note or delete_change. It clearly identifies the resource as a ticket.

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 explicitly state when this tool should be used versus alternatives. The mention of 'soft delete' implies usage for non-permanent deletions, but no alternative is named and no exclusion or prerequisite is given. Usage guidance is only implied.

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