Get Kanban Columns

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

No annotations are provided, so the description must carry the transparency burden. It indicates a read-only list operation by using 'List', and adds the kanban constraint. However, it does not disclose what happens for non-kanban projects (e.g., empty list vs. error) or any return format details.

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 two short sentences with no redundant information. It is front-loaded with the key action and resource, and the second sentence adds a necessary constraint. Zero waste.

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 the low complexity (single param, no output schema), the description explains the primary purpose and applicability. However, without an output schema it does not describe what a column object looks like or the shape of the response, leaving some contextual gaps.

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 schema already describes project_id as 'The project ID' with 100% coverage. The description adds no extra meaning beyond what the schema provides, so the baseline 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 (List), the resource (all Kanban columns for a project), and the scope (per project). It also distinguishes itself from siblings by noting it is only for kanban view mode, which is a specific constraint.

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 provides a clear usage condition by stating 'Only applicable to projects using kanban view mode.' It implies when to use this tool, though it does not name alternative tools for non-kanban projects or explicitly exclude other cases.

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