tasks_clear

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

With no annotations provided, the description must disclose behavioral traits. It states it clears 'completed tasks' but fails to mention if the action is irreversible, requires write permissions, or affects non-completed tasks. This is a significant 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, efficient sentence with no wasted words. It front-loads the action and resource. Slightly more context could be added (e.g., 'This action cannot be undone') without harming conciseness.

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?

Given the lack of annotations, output schema, and the destructive nature of the tool, the description is inadequate. It omits details about irreversibility, permissions, and appropriate context (e.g., when to use instead of tasks_delete). A more complete description would include these safety-critical aspects.

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 coverage is 100% for the single parameter, and the description adds value by noting 'use '@default' for the default list'. However, it does not provide additional semantics beyond that hint, so it meets the baseline without excess.

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 'Clear all completed tasks' and the resource 'task list', distinguishing it from sibling tools like tasks_delete (deletes specific tasks) and tasks_complete (marks tasks as completed). The verb 'clear' is specific and 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 implies usage for removing completed tasks from a list but lacks explicit guidance on when to use vs alternatives (e.g., tasks_delete for individual tasks), prerequisites (e.g., task list must exist), or warnings about irreversibility. No exclusions or alternative tool mentions.

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