list_buckets

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

Discloses that only columns are returned (no tasks), board order is preserved, and explains the limit field semantics. With no annotations, this provides good transparency, though it does not address potential errors or permissions.

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?

Two concise paragraphs, one covering purpose and one covering limit semantics. No redundant content, though the repeated reference to 'list_board' could be tightened.

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?

Provides sufficient context to choose the tool and understand its output compared to list_board. The presence of an output schema mitigates the need to describe return values, but the parameter descriptions are thin.

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 0%; the description only says 'takes the same arguments' as list_board without explaining project_id or view_id directly. The agent must infer their meaning from sibling context, which is insufficient.

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 it lists the columns of a project's kanban view in board order, and distinguishes itself from list_board by noting it returns columns without 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?

Explicitly contrasts with list_board, which returns each column with its tasks, and mentions both take the same arguments, giving the agent clear guidance on when to use each.

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