delete-planner-bucket

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

Annotations already indicate destructiveHint=true. The description adds the important behavioral detail that the tool requires an ETag via the If-Match header, which is not covered by annotations. However, it does not mention other behavioral aspects like whether the deletion is reversible or what the response indicates.

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 with only two short sentences. The critical tip is front-loaded with emoji emphasis, and every sentence provides essential information without 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 the lack of an output schema, the description adequately covers the key prerequisite (ETag). It does not explain the response format or successful deletion behavior, but the combination of annotations (destructiveHint=true) and the tip is fairly complete for this destructive operation.

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 100% description coverage for all 4 parameters. The description adds value by explaining the purpose of the includeHeaders parameter in the context of obtaining the ETag. However, it does not add meaning to the required plannerBucketId parameter beyond what the schema provides.

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 clearly states 'Delete plannerBucket' using a specific verb and resource. It distinguishes from sibling tools like create-planner-bucket and update-planner-bucket by explicitly stating the delete action.

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 a critical tip explaining the requirement for an If-Match header with the ETag from get-planner-bucket and advises using includeHeaders=true. This tells the agent when and how to use the tool, including a prerequisite (calling get-planner-bucket first).

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