create-planner-bucket

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

Annotations already indicate readOnlyHint=false and destructiveHint=true, signaling a write operation with potential side effects. The description adds no additional behavioral context beyond what the annotations provide, such as authentication needs, rate limits, or details on what state changes occur.

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 sentence that directly states the tool's purpose with no wasted words. It is appropriately sized and front-loaded, making it easy for an agent to quickly grasp the function.

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 with nested objects and the lack of an output schema, the description is insufficient. It does not explain the bucket's role, required parameters beyond what the schema provides, or the format of the response. The tool's behavior after creation is not addressed.

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?

The input schema has 67% description coverage, with detailed descriptions for key properties like 'name' and 'planId'. The description adds no extra meaning beyond the schema, so it meets the baseline for high coverage but does not improve 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 'Create a new plannerBucket object.' clearly states the action (create) and the resource (plannerBucket). It is specific and unambiguous, but does not explicitly differentiate from sibling tools like 'update-planner-bucket' or 'delete-planner-bucket', though the name itself provides that distinction.

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 versus alternatives such as 'update-planner-bucket' or 'create-planner-task'. There are no prerequisites, context, or exclusion criteria mentioned, leaving the agent to infer usage from the tool name alone.

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