Manage Task

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

The annotations already declare readOnlyHint=false and destructiveHint=true, so the description need not restate that this is a mutating tool. It does add the specific actions (create, update, delete, move), but it does not disclose side effects, permission requirements, or reversibility beyond what annotations provide.

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 a front-loaded verb and a concise action list. There is no wasted wording or redundant elaboration.

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 action list plus the richly documented 100%-covered input schema and existing output schema make the definition largely sufficient for correct invocation. It could be slightly more complete with explicit alternatives, but that gap is minor given the schema and annotations.

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 100%, and each parameter has a detailed description including which actions use it. The tool description itself adds no parameter-level meaning, so the baseline of 3 applies.

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 clear verb and resource: 'Manage tasks: create, update, delete, or move tasks within task lists.' It explicitly enumerates the supported operations and distinguishes this tool from sibling read-only tools like list_tasks/get_task and from task-list management via manage_task_list.

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 task CRUD and moving operations, but it does not explicitly state when to use this tool versus alternatives such as list_tasks or get_task. There are no exclusions or routing guidance like 'for reads, use list_tasks instead.'

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