create-planner-task

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

Annotations indicate destructiveHint=true, consistent with the description's 'Create'. However, the description does not disclose any additional behavioral traits (e.g., permissions required, side effects, or default values). No contradiction, but minimal added value beyond annotations.

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 extremely concise (5 words) with no fluff. It is front-loaded with the essential action, but could benefit from a bit more context without losing 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 tool's complexity (nested input, many parameters, no output schema), the description is severely incomplete. It does not explain the purpose of the task, required fields, or how it relates to plans, buckets, or sibling tools.

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 67%, meaning many parameters have descriptions. The description adds no information about parameters or how to use them, missing an opportunity to clarify the complex nested body object or required fields.

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 'Create a new plannerTask' clearly states the action (create) and the resource (plannerTask). It distinguishes from sibling tools like 'create-planner-bucket' or 'create-todo-task' by the resource name, but does not provide additional context about what a planner task entails.

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 provides no guidance on when to use this tool vs alternatives, nor does it mention prerequisites (e.g., needing a plan ID or bucket ID). No when-not-to-use or context is given.

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