delete_task

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

The description discloses that deleting a task will also delete all its child tasks, and lists possible error types. With no annotations provided, these behavioral details are important and adequately covered.

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 short and front-loaded with the main action, but it contains slight redundancy (two similar sentences about using SOAP). The Args/Returns/Raises structure is well-organized.

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?

Given the tool's simplicity (single parameter, no output schema), the description adequately covers side effects (child deletion), parameter format, error conditions, and return type. It does not fully explain the return dict structure, but this is acceptable without an output schema.

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?

Despite the schema having 0% coverage, the description's Args section adds significant meaning: it specifies the parameter format (key://, search://, or ekey:// URIs) and describes its role beyond the schema's type 'string'.

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 explicitly states 'Delete a task using SOAP TaskService.' It clearly identifies the action (delete) and resource (task), and distinguishes itself from siblings like batch_delete_tasks and delete_project.

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 includes a note that Beta MCP cannot delete tasks, which implies when not to use it. However, it lacks explicit guidance on when to use this tool over alternatives like batch_delete_tasks or delete_project, and does not provide context for prerequisites.

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