admin_delete_worksheet

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

Without annotations, the description carries the full burden of disclosing behavioral traits. It indicates that the operation is a DELETE (mutation) and requires confirmation, but it does not disclose whether the operation is irreversible, error conditions, or what happens to related data.

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 consists of two short sentences, front-loading the action ('DELETE'). Every word is necessary and there is no redundancy. It is exceptionally concise.

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 destructive tool with 3 parameters and no output schema, the description is adequate but not complete. It covers the basic action and the confirmation requirement, but lacks information on idempotency, error handling, or post-deletion effects.

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 the baseline is 3. The description adds emphasis on the 'confirmed' parameter ('The user MUST confirm') but does not add meaning to 'ticket_id' or 'id' beyond their schema descriptions. It does not exceed the schema's value.

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 'DELETE a worksheet result', specifying the verb (DELETE) and the resource (worksheet result). This distinguishes it from sibling tools that delete other resources like canned responses or portal users.

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 only provides minimal guidance by stating that user confirmation is required ('The user MUST confirm'). It does not mention when to use this tool versus alternatives, nor does it cover prerequisites or potential side effects.

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