tasks_clear_completed

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

With no annotations provided, the description carries the full burden. 'Clear' implies deletion but the description does not state that the operation is destructive/irreversible, what effects it has on the task list, or any permissions needed, so behavioral disclosure is minimal.

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?

A single sentence of 8 words, with no filler. It is front-loaded with the action and resource, and every word earns its place.

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?

While the tool is simple, the description lacks critical context: it does not mention the input parameter's role, default behavior, or any side effects. An output schema exists but its content is not provided, so the description still needs to convey behavioral context. Overall, it covers the basic action but leaves important 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% for the sole parameter tasklist_id. The description vaguely references 'a task list' but does not explicitly map the parameter, explain the default '@default' value, or clarify required vs optional. Thus it fails to compensate for the missing schema details.

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 'Clear all completed tasks from a task list' uses a specific verb ('clear') and resource ('completed tasks'), and scopes it to a task list. It clearly distinguishes from siblings like tasks_delete (which might delete tasks individually) and tasks_update (which updates tasks).

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. It doesn't mention that tasks_delete should be used for individual task removal or any exclusions/conditions, leaving the agent without decision support.

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