kaiten_list_columns

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

Annotations are absent, so the description carries the full burden. It discloses the meaning of column type codes and lists key response fields, which helps an agent interpret the output. However, it does not explicitly state that the operation is read-only or describe any error conditions, though the 'list' verb implies a safe read.

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, two sentences, with the primary purpose in the first sentence and supplementary details (column types and response fields) in the second. It is front-loaded and every sentence adds value.

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 there is no output schema, the description compensates by listing key response fields and explaining column type semantics. It is reasonably complete for a single-parameter list operation, though it could mention pagination or errors. Overall, it provides enough for an agent to call it correctly.

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% with the parameter board_id already described as 'Board ID'. The description does not add any extra meaning about parameters beyond the schema, staying at the baseline for high coverage.

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 verb 'List' and the resource 'columns on a Kaiten board', which is specific and unambiguous. It distinguishes itself from other list tools by naming the exact resource, and the column types detail adds clarity about what constitutes a column.

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 on when to use this tool versus alternatives, such as kaiten_list_boards or kaiten_create_column. There is no mention of prerequisites (e.g., needing a valid board_id) or when this tool should be preferred over other list operations.

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