subtask_delete

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

The annotations already declare destructiveHint: true and idempotentHint: true. The description adds that multiple IDs can be deleted, but does not elaborate on whether deletion is permanent, cascades, or affects related resources. It does not contradict annotations.

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 a single sentence, concise and to the point. It could be slightly more informative without losing conciseness, but it avoids unnecessary verbosity.

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, the description and annotations cover basics (destructive, idempotent, accepts IDs). However, it lacks details on return value (should be noted given no output schema), side effects, or error conditions. Adequate but not fully 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 input schema has descriptions embedded in the oneOf branches, but the parameter 'ids' itself lacks a high-level description. The description adds minimal value by explaining that it accepts a single ID or array, which is already covered by the schema. Schema description coverage is 0% per context, but the description partially compensates.

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' and the resource 'subtasks', distinguishing it from siblings like subtask_create and subtask_update. It specifies that it can handle a single ID or array of IDs.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., subtask_update or other delete tools). There is no mention of prerequisites, such as required permissions or links, or cautions about accidental deletion.

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