cigchat_team_ticket_lists_delete

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

With no annotations provided, the description carries full burden. It discloses irreversibility, the confirmation process, and required token scope. It does not describe the impact statement contents or post-delete behavior, but covers core behavioral safety.

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, dense sentence that front-loads the verb and resource, then states the endpoint, destructive warning, confirmation procedure, and scope requirement. Every clause earns its place.

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 delete tool with no output schema, the description covers purpose, safety, confirmation flow, and auth requirement. It lacks detail about what the impact statement contains or the final response, but is largely complete for 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 coverage is 100%, so baseline is 3. The schema already describes the 'confirm' token flow, and the description reinforces it but does not add substantial meaning beyond what the schema provides. listId and listItemId remain minimally described.

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 a ticket' and includes the exact endpoint. It distinguishes this tool from siblings like update/create/list operations and clearly signals its destructive nature.

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 provides explicit usage guidance: call once without 'confirm' to get an impact statement first, and requires the 'Manage Team' scope. It does not explicitly mention alternatives, but the destructive confirmation flow is strongly contextual.

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