delete_subtask

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

Annotations already indicate destructiveHint: true, but the description adds valuable context: soft-delete mechanism, server-side retention, MCP-visible effect, and specific failure modes. This goes beyond what annotations provide.

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 with three short paragraphs, each serving a purpose: stating the action, explaining soft-delete behavior, and listing failure modes. No redundant information.

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 single parameter, existing output schema, and annotations, the description covers behavior, side effects, failure modes, and recommended follow-up actions. It provides complete context for an agent to use this tool correctly.

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 description coverage, the description does not elaborate on the subtask_id parameter beyond its existence. The schema already defines it as an integer >=1, but the description could have added context about how to obtain the ID (e.g., from list_subtasks). Score is baseline due to minimal additional meaning.

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 a subtask (soft-delete)' with a specific verb and resource. It distinguishes from sibling tools like archive_task by clarifying it applies to subtasks only and uses soft-delete semantics.

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 when to use this tool (when needing to soft-delete a subtask) and includes failure modes (404 for unknown or already deleted subtask) with a recommendation to re-fetch parent task's subtasks list. While it doesn't explicitly exclude alternatives, the context is clear enough for an agent.

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