delete_bucket

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

With no annotations provided, the description carries the full behavioral disclosure burden. It transparently explains that tasks are moved to the default bucket and left intact, and that the last column cannot be removed. This is strong disclosure of side effects and invariants, though it does not mention permissions or error responses.

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 concise, well-structured, and front-loaded with the primary purpose. The supporting details about task migration and the last-column constraint are directly relevant and add no fluff.

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?

The description explains the behavioral outcome well but is incomplete for invocation. A caller cannot confidently determine how view_id should be used when multiple kanban views exist, and there is no output schema or annotation to offset this. The tool has only three parameters, so a complete definition should clarify each one or at least explain the view_id relationship.

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 0%, and the description does not explain the three parameters. It loosely implies that project_id identifies the project and bucket_id identifies the column, but the optional view_id is completely unexplained. This is a meaningful gap because the distinction between bucket_id and view_id is not obvious.

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 a specific action and resource: 'Delete a column from a project's kanban view.' It equates bucket with column, which distinguishes it from other deletion tools like delete_task or delete_label. The behavior is immediately understandable.

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 conveys when to use the tool by defining the delete action and including the constraint that the last column cannot be removed. However, it does not explicitly mention alternatives or when-not-to-use conditions, such as using move_task_to_bucket if tasks should be relocated manually. The guidance is implied rather than direct.

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