create-planner-task

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds no additional behavioral context, such as side effects, permission requirements, or response characteristics.

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 single-sentence description is concise and front-loaded, but it is too short to be informative. While there is no wasted text, it does not earn its place by adding 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?

Given the complex input schema (many nested objects) and no output schema, the description is highly incomplete. It does not explain minimal requirements, typical usage, or how the returned object looks.

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 75% (three of four top-level parameters have descriptions), but the tool description adds no parameter information. The body parameter lacks a description in the schema, and the description does not compensate by explaining required fields like title or planId.

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' states the basic verb+resource but is essentially a tautology of the tool name. It does not differentiate from sibling tools like create-planner-bucket or create-planner-task-message, nor does it clarify what a plannerTask is.

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?

No guidance is provided on when to use this tool versus alternatives, required prerequisites (e.g., needing a planId), or caveats. Siblings like create-planner-task-message exist without any differentiation.

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