kaiten_delete_card_blocker

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only restates the destructive action already implied by the tool name. It does not explain whether deletion is permanent, affects other data, or has permission requirements.

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, clear sentence with no filler or unnecessary detail, which suits a simple two-parameter tool. It is concise but does not add much beyond what the tool name already communicates.

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 is minimally adequate: an agent can identify the operation and the required IDs from the schema and tool name. However, it lacks useful context such as whether deletion is irreversible, what the response looks like, or how this relates to other blocker operations. Given no annotations or output schema, this is a moderate gap.

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 description adds no parameter-specific meaning, but the input schema fully documents both required parameters with 100% coverage. Since the schema handles parameter semantics, the baseline score of 3 is appropriate.

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 the action ('Delete'), the resource ('a blocker'), and the scope ('from a card'), making it immediately distinguishable from sibling operations like create, get, update, or list blocker. The meaning is unambiguous and specific.

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 about when to use this tool versus alternatives such as kaiten_create_card_blocker or kaiten_update_card_blocker. There is no mention of prerequisites, workflow context, or when deletion would be appropriate.

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