delete_done_tasks

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

No annotations are provided, so the description must disclose behavioral traits itself. It only says 'Alias for deleting completed download tasks,' which adds little beyond the tool name and does not explain side effects, irreversibility, or how the 'force' parameter alters behavior. The word 'Alias' implies equivalence with another operation but does not specify what that operation entails.

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 with no redundant wording and the main action is front-loaded. It is concise, though that conciseness comes at the cost of omitting parameter semantics. As a structure, it is clean, but not fully informative.

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 deletion tool with no annotations and a parameter that is undocumented everywhere, the description is incomplete. It does not explain 'force', the difference from delete_completed_tasks, or any postconditions of the operation. The presence of an output schema helps with return values but not with these 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?

Schema description coverage is 0%, and the description does not mention the 'force' boolean parameter at all. The input schema only provides a title and default, leaving the parameter's meaning entirely unexplained. The description fails to compensate for the missing parameter documentation.

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 verb and resource: 'deleting completed download tasks.' It is not a tautology and an agent can tell what action occurs. However, it does not differentiate from the sibling tool delete_completed_tasks, and the word 'Alias' signals that it may be a duplicate rather than a distinct 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 gives general context—this affects completed download tasks—but it provides no explicit when-to-use or when-not-to-use guidance. Given the sibling delete_completed_tasks, there is no direction about which tool to prefer or how these two relate. The agent must infer the intended usage from the name alone.

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