kaiten_list_card_blockers

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

No annotations are provided, so the description carries the full behavioral burden. It only restates the operation and says nothing about response format, pagination, ordering, permissions, or side effects. 'List' implies a read operation, but no further behavioral detail is disclosed.

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 front-loaded sentence with no filler or repetition. This is appropriately minimal for a one-parameter tool, although the brevity comes at the cost of missing behavioral and usage context.

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?

For a simple one-parameter read tool with a fully documented schema, this is nearly sufficient to invoke correctly. However, with no annotations and no output schema, an agent gets no information about return shape, auth requirements, or how this differs from the single-blocker getter, leaving selection and expectation-setting incomplete.

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 coverage is 100%, and the single card_id parameter is already described as 'ID of the card whose blockers to list.' The description adds no meaning beyond the schema, so it meets the baseline but does not exceed 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 uses a specific verb ('List') and resource ('all blockers on a card'), clearly identifying the operation. It does not explicitly distinguish from kaiten_get_card_blocker, but the word 'all' conveys that this is the list variant.

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 gives no guidance on when to use this tool versus alternatives like kaiten_get_card_blocker or kaiten_create_card_blocker. There are no exclusions, prerequisites, or context clues beyond the tool name and basic verb.

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