Manage Task List

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description confirms destructive actions like 'delete' and 'clear_completed', but adds no new behavioral context beyond what annotations provide (e.g., permission requirements or irreversible effects).

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 one concise sentence, front-loaded with the verb and resource, and contains no unnecessary words. It efficiently communicates the core functionality.

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 tool's complexity (4 actions with conditional parameter requirements), the description lacks critical execution context. It does not explain that task_list_id is required for update/delete/clear_completed, nor that title is needed for create/update. This omission hampers correct invocation despite having an output schema.

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%, so the input schema already documents all parameters. The description only lists action values, which are also included in the schema description. It does not clarify which parameters are required for each action, leaving that to the schema.

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 tool's function with a specific verb 'Manage' and resource 'task lists', listing all four possible actions (create, update, delete, clear_completed). This distinguishes it from sibling read-only tools like 'get_task_list' and 'list_task_lists', and from 'manage_task' which handles individual 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?

The description implicitly conveys usage for mutating task lists, but it does not explicitly state when to use this tool versus alternatives (e.g., for reading, use 'get_task_list'). No guidance is given on prerequisites or when actions are appropriate.

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