manage_task

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

No annotations provided, so description carries full burden. Discloses side effects (mutates state), special behavior (move reparents/relocates), and OAuth requirement. Lacks details on error handling or deletion cascading, but sufficient for typical CRUD.

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?

Three concise sentences with front-loaded purpose, followed by side effects, usage tip, sibling reference, and auth requirement. Every sentence earns its place with no redundancy.

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 11 parameters and 4 actions with no annotations, description covers actions at high level, provides specific usage tips, and references sibling tool. Output schema exists, so return details not needed. Minor gaps: could mention error handling, but overall complete.

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 baseline 3. Description adds value beyond schema by clarifying usage patterns (e.g., completing task, ordering via 'previous'), improving parameter understanding.

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 explicitly states the tool creates, updates, deletes, or moves tasks, with clear verb+resource. It distinguishes from manage_task_list by noting 'For list-level operations use 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?

Provides when-to-use context (e.g., completing a task via action='update' with status='completed') and a sibling tool reference (manage_task_list). Does not explicitly exclude read-only alternatives like get_task or list_tasks, but usage is implied.

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