list_columns

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

No annotations provided, so the description carries full burden. It correctly indicates a read operation ('list') but does not disclose any potential side effects or behavioral traits beyond the basic listing function.

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?

Concise one-sentence description plus structured metadata and args. Front-loaded with purpose. The args section adds slight redundancy but is acceptable.

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?

Has an output schema (not shown) and one clearly described parameter. The description adequately covers what the tool does and the prerequisite for the project to have kanban view mode. No missing context for a simple listing tool.

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?

With 0% schema description coverage, the description adds meaning by stating 'The project with kanban view mode', clarifying that the project must have kanban columns. This adds value beyond the schema's generic 'string' type.

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?

Clearly states 'List kanban columns for a project', specifying the verb and resource. Distinguishes from siblings like 'manage_columns' which likely does more than listing, and 'get_project_tasks' which focuses on tasks.

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?

Provides related tools in metadata but no explicit when-to-use or when-not-to-use. The parameter description implies the project must have kanban view mode, giving a usage condition, but lacks clear alternatives or exclusions.

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