delete_subtask

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

With no annotations provided, the description carries full burden for behavioral disclosure. It reveals the critical behavior that confirm=true is required for deletion, which is a safety guard. However, it does not disclose whether deletion is permanent, any permissions needed, or potential cascading effects, leaving the agent with limited understanding of the operation's consequences.

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 exceptionally concise, consisting of two short sentences. While it is front-loaded and waste-free, it is so terse that it sacrifices necessary detail. The structure is acceptable, but the brevity borders on under-specification, warranting a middle score.

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 annotations, no output schema, and four parameters, the description is incomplete. It mentions the critical confirm requirement but omits other context like the hierarchical relationship between project, work item, and subtask, or any expected side effects. This leaves the agent with insufficient information to fully understand the tool's behavior.

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 schema has 0% description coverage for parameters. The description only adds meaning for the confirm parameter, specifying that it must be true. It does not explain project_id, work_item_id, or subtask_id, though these names are self-explanatory due to the tool's context. This partial compensation is insufficient given the complete lack of schema descriptions.

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 sub-task,' which identifies a specific verb and resource. It distinguishes from sibling tools like delete_work_item or delete_project, but it doesn't explicitly differentiate from add_subtask/update_subtask/list_subtasks beyond implying the delete operation.

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 provides no guidance on when to use this tool versus alternatives. The only usage-related information is the requirement that confirm=true, but this is more of an invocation requirement than a contextual guideline about when to choose this tool.

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