weeek_list_board_columns

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description doesn't state whether this is a read-only operation, what the response format looks like, whether columns are returned in a specific order, or whether the operation requires specific permissions. For a listing tool with zero annotation coverage, this is a notable gap.

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 short sentences with no filler. The parenthetical clarification that columns are 'statuses' is genuinely useful terminology mapping. The tool is simple enough (1 param) that this level of brevity is appropriate, and there's minimal 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?

For a simple list tool with a single required parameter, this is nearly adequate. The description explains the resource and the required parameter. However, the lack of output schema, no annotations, and no mention of related error cases or pagination behavior leave some gaps. The tool is simple enough that these gaps are somewhat tolerable, but a note about what 'columns' returns and their relationship to tasks would improve completeness.

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 only 1 parameter at 0% schema description coverage, the description should compensate. The description does mention that board_id is required by the Weeek API, which reinforces the schema's required field declaration, but adds little beyond what the input schema already states about board_id being required. It doesn't explain what a valid board_id is or how to obtain it.

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 states 'List board columns (statuses) for a board' which uses a specific verb (list) and resource (board columns), clarifying that columns are synonymous with statuses. However, it doesn't distinguish itself clearly from sibling tools like weeek_list_boards or weeek_manage_board_columns, though the verb+resource distinction is somewhat implied by the naming convention.

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 only notes that board_id is required, which is a parameter constraint rather than usage context. There's no mention of when this tool should be preferred over weeek_manage_board_columns, which relates to the same resource with a different verb, nor any prerequisites like needing to list boards first to get a valid board_id.

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