create-planner-task

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

Annotations already indicate a destructive hint (destructiveHint=true) and non-read-only. The description adds no additional behavioral context, such as required authentication, side effects, or constraints beyond the action name.

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 very concise (one sentence), which aids quick scanning, but it lacks any additional structure or detail. It is under-specified for a complex tool with many parameters.

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 (nested object with many properties) and no output schema, the description is far too minimal. It does not explain required fields, dependencies (e.g., planId and bucketId), or return information, leaving significant gaps in understanding.

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 67%, so the schema itself documents many parameters. The description does not add any extra meaning about which parameters are essential or how they relate to the action, meeting the baseline but not exceeding it.

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 specifies the action and resource. However, it does not differentiate from sibling tools like create-planner-bucket or update-planner-task, nor does it mention any scope or context.

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. Prerequisites (e.g., existing plan and bucket) are not mentioned, leaving the agent without critical context for correct invocation.

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