Delete Task

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

The description reinforces the destructive nature (destructiveHint=true) by stating 'cannot be undone' twice and 'Permanently removes'. There is no contradiction with annotations, and it adds emphasis beyond the annotation hints.

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 relatively short and front-loaded with the main action. However, it repeats 'cannot be undone' and 'Schedule (Legacy)' multiple times, which could be streamlined slightly.

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 the action, permanence, required parameters, and API endpoint. It lacks details about error states or what happens on success, but overall it is adequately complete.

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?

The description names the required parameters ('id, project_id') but does not add additional meaning beyond what the input schema already provides. Since schema coverage is 100%, this score is appropriate.

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 the specified Task'), identifies the resource as Schedule (Legacy) records, and emphasizes permanence. It effectively differentiates from other tools by specifying the exact function.

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 states when to use the tool ('permanently delete the specified Schedule (Legacy) records') and lists required parameters. However, it does not provide guidance on when not to use it or alternatives, which keeps it from a higher score.

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