delete task

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a destructive write. The description adds nothing beyond that—no mention of permanence, cascade effects, required permissions, or recovery options. For a destructive operation, more behavioral context would be valuable.

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?

Single, efficient sentence with no waste. Front-loaded with the action and target. Could be slightly more informative but is appropriately sized.

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 tool with no output schema, the description is too thin. It omits critical details like what happens on success/failure, whether the task is permanently removed, and any side effects. Annotations cover the safety profile but the description should still provide operational context.

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 0%, so the description must compensate but doesn't. It doesn't clarify that 'uuid' identifies the task to delete or its format. However, with only one required parameter and the schema naming it clearly, the baseline of 3 is defensible, though the description should do more.

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?

Clear verb+resource: 'Delete a task from the task repo system.' An agent knows exactly what this tool does. It does not, however, differentiate itself from siblings like update_task_status or create_task, though the delete action is inherently distinct.

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 when-to-use guidance, no prerequisites, no alternatives mentioned. The description simply states the action without context about when deletion is appropriate vs. archiving or status changes.

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