batch_delete_tasks

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

No annotations exist, so the description carries full burden. It discloses non-atomicity and per-key success/failure returns, which is valuable. However, it does not describe output format, error conditions, permissions, or rate limits. The behavioral disclosure is adequate but not comprehensive.

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 concise (3 sentences) and well-structured, starting with operational context, then action, then behavioral note. Every sentence adds value, and it avoids verbosity. Slightly more could be trimmed, but it's effective.

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 1 parameter and no output schema, the description covers purpose and key behavioral aspects (non-atomicity, retry logic). However, it omits response structure, error handling, and prerequisites. The agent likely needs more detail to correctly invoke and interpret results, leaving gaps.

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?

With 0% schema coverage, the description should compensate but only mentions 'task_keys' as the parameter. The name is self-explanatory, but no format, constraints, or examples are provided. The description adds minimal value beyond the parameter name, leaving the agent to infer semantics.

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 multiple tasks in bulk using the SOAP TaskService.' It clearly identifies the action (delete), resource (multiple tasks), and distinguishes from siblings like delete_task (singular) and batch_create_tasks. The note about Beta MCP inability to delete tasks adds operational context.

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 explains non-atomic behavior and provides retry guidance: callers can safely retry only failed keys. This helps usage decisions. However, it does not explicitly contrast with delete_task for single deletions or state when not to use this tool (e.g., if atomicity is required).

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