delete_butler

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

Annotations already mark destructiveHint=true and readOnlyHint=false, and the description aligns with them. It adds the useful semantic of 'stop' rather than just 'delete', but does not disclose side effects, whether running tasks are cancelled, or any confirmation behavior. No contradiction with annotations.

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?

Extremely short and front-loaded: a one-sentence purpose plus the endpoint line. No filler, and the endpoint adds useful operational detail without bloat.

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 zero-parameter destructive operation with output schema and safety annotations, the description is mostly sufficient. It names the full scope ('all tasks') and the operation; the main gap is lack of context about what Butler tasks are and the targeted alternative.

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?

There are zero parameters, so baseline 4 applies. The phrase 'all Butler tasks' also reinforces why no target parameter is needed.

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?

Clearly states the action 'Stop' and the exact resource ('all Butler tasks'). The word 'all' differentiates it from the sibling delete_butler_by_butler_task, which targets a single task, and the endpoint line confirms the DELETE verb.

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?

No guidance on when to use this tool versus alternatives like delete_butler_by_butler_task, list_butler, or create_butler. The only hint is the word 'all', but there is no explicit when/when-not or alternative routing.

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