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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly labels the operation as 'DESTRUCTIVE' and warns to confirm first, which is meaningful for an AI agent. It stops short of explaining reversibility or side effects, but the soft-delete wording gives useful nuance.

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 entire description is one short, front-loaded sentence with no wasted words. The core action comes first, followed immediately by the destructive warning.

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 single-parameter delete operation with no output schema, the description covers the essential information: what action is performed and that it is destructive. It is concise but does not mention restoration options or what happens after deletion, leaving a minor gap.

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 and the only parameter, id, is not explained. The description does not explicitly state that id identifies the task to delete, though the tool name and purpose make that inference fairly easy. This falls short of compensating for the missing schema description.

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 states a specific verb ('Soft-delete') and a specific resource ('a task'), which clearly identifies what the tool does. It is naturally distinct from sibling tools like tasks_complete, tasks_get, tasks_list, and tasks_update.

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 instruction 'confirm first' provides operational guidance, and the purpose implies it should be used when a task needs to be deleted. However, it does not explicitly name alternatives, such as tasks_complete for finishing a task, or state when not to use this tool.

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