tasks_tasks_clear

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

Description adds beyond annotations: clarifies that clearing hides, not deletes, tasks. Annotations indicate destructive=true, readOnly=false, which align. No contradictions.

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?

Two concise sentences, no wasted words, front-loaded with action. Every sentence adds value.

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?

Simple tool with one parameter, no output schema. Description explains key behavioral nuance (hide vs delete) and purpose. Sufficient for invocation.

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 already describes 'tasklist' as 'Task list ID to clear'. Description adds no extra parameter info. Baseline 3 since schema coverage is 100%.

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 'Hide' and resource 'all completed tasks in a list'. It distinguishes from deletion by noting tasks are not deleted but stop appearing in default responses.

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?

Implies usage for hiding completed tasks, but no explicit when-to-use or alternatives. Sibling tools like tasks_tasks_delete are not mentioned, leaving the agent to infer differentiation.

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