delete_ticket_group

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only states 'Delete a ticket group,' which implies destructive action but does not specify irreversibility, side effects on associated tickets or events, permissions required, or what the output represents. For a destructive tool, this is severely inadequate.

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 very short, but this is under-specification rather than concise effectiveness. It adds no value beyond the tool name and does not front-load any critical information. The brevity is not earned because it omits essential context.

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 tool with a single parameter and destructive action, the description should explain what a ticket group is, the consequences of deletion, and any prerequisites. It does none of this. Even though an output schema exists, the description leaves the agent without enough information to safely invoke the tool. Completely inadequate.

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%, and the description does not mention the parameter 'ticket_group_id' at all. It adds no meaning beyond what the schema field name implies. There is no guidance on the format, source, or validation of the ID. The description fails to compensate for the lack of schema documentation.

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 states a clear verb and resource: 'Delete a ticket group.' It is unambiguous about the action, but it does not differentiate from sibling tools like delete_event or delete_discount beyond the object type. Since it is clear but lacks sibling differentiation, a score of 4 is appropriate.

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 guidance on when to use this tool, prerequisites, or alternatives. It does not mention any conditions for deletion (e.g., whether the ticket group must be empty or have no associated events), nor does it direct the agent to related tools like get_ticket_group for verification. No usage context is provided.

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