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 of behavioral disclosure. It states 'Clear all completed tasks' which implies a destructive, irreversible action, but it does not explicitly warn that tasks will be permanently deleted, mention any auth requirements, or describe the effect on the task list. This is a significant transparency gap for a mutation tool.

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 filler words, making it efficient and front-loaded. However, it is almost too terse—for a destructive operation, additional context would be expected, but the conciseness itself is not penalized heavily because 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?

The tool is simple (one parameter, output schema exists), but the description is minimal. It fails to explain the permanence of the clear action, whether it only affects the specified list, or any side effects. Given that there are no annotations and the description is the only source of behavior, it is insufficiently complete even for a straightforward operation.

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%, so the description must compensate. It mentions 'from a task list' which implies that tasklist_id identifies the target list, but this is already evident from the parameter name. It adds no details about the default value ('@default'), whether the parameter is required (it is not), or how the clear operation scopes to that list. The parameter semantics are barely enriched.

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 uses a specific verb ('Clear') and identifies the resource ('all completed tasks from a task list'), clearly distinguishing it from sibling tools like tasks_delete (which removes individual tasks) or tasks_update (which modifies tasks). The action is unambiguous.

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 explicit guidance on when to use this tool versus alternatives. While the sibling context implies it is for bulk-removing completed tasks rather than deleting them individually, the description itself does not state any use cases, exclusions, or prerequisites (e.g., the need for a specific tasklist_id).

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