Delete Task

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

Beyond annotations (destructiveHint: true), the description discloses that deletion is permanent, cannot be undone, repeat calls return 404, and failures return error payloads with HTTP status codes (401, 403, 404). This is rich behavioral context that fully informs the agent of consequences and error handling.

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 well-structured and front-loaded, starting with the action, then prerequisites, effects, error handling, required parameters, and API location. Every sentence delivers value without redundancy or fluff.

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 delete operation with no output schema, the description covers all necessary context: prerequisites (resolve id), destructive effects, idempotency behavior (404 on repeat), common error statuses, required parameters, and endpoint details. It is complete for an agent to safely invoke the tool.

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%, but the description adds meaningful semantics: it explains that 'id' must identify an existing parent record and should be resolved with the matching list tool. This goes beyond the schema's simple type/description, enhancing understanding of how to populate the parameters correctly.

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 the specified Task' with a specific verb and resource, and adds context by referencing the Schedule (Legacy) API and endpoint. It distinguishes from sibling tools by specifying the target resource (Task) and noting the need to resolve the id via show/list tools.

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 explicitly instructs to 'Confirm the target id with the matching show or list tool before calling' and explains the id must resolve to an existing parent record. This provides clear when-to-use guidance, though it does not explicitly enumerate alternative delete tools or scenarios where deletion is inappropriate.

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