kaiten_list_subcolumns

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

With no annotations provided, the description carries the full disclosure burden. 'List all' indicates a read-only operation with broad scope, which is helpful, but it does not disclose pagination behavior, ordering, return format, or potential size limitations. It provides some behavioral context but leaves meaningful gaps.

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 sentence with no filler and the key fact is front-loaded: 'List all subcolumns of a Kaiten column.' Every word contributes to meaning, making it an appropriately concise definition.

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 single-parameter read tool, the description is minimally sufficient but leaves gaps. There is no output schema, so return fields are not described, and pagination or large-result behavior is not mentioned. However, the operation is simple and the required parameter is fully documented, so the definition is adequate but not exceptional.

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 100%: column_id is documented as 'Column ID'. The description does not add meaning beyond that, such as how to find a valid column_id or whether the column must belong to a specific board or space. Baseline 3 is appropriate because the schema already fully documents the only parameter.

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 the specific verb 'List' and the resource 'subcolumns of a Kaiten column,' making the operation unambiguous. It clearly distinguishes this tool from siblings like kaiten_list_columns, kaiten_create_subcolumn, and kaiten_update_subcolumn by focusing on the subcolumn list operation.

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 when-to-use guidance is provided. The description does not mention alternatives or conditions that would make this tool preferable, such as distinguishing it from kaiten_list_columns or noting that a column_id must first be known. Usage must be inferred entirely from the tool's name and minimal description.

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