List Weeek columns for a board

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds useful context: returns all columns in upstream sort order and emphasizes that 'the array order is the signal.' This goes beyond annotation hints and clarifies a key behavioral trait.

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 front-loaded and information-dense. The first sentence states purpose and return shape, the second adds usage context. The parenthetical return shape detail might be slightly redundant with the output schema, but it serves immediate comprehension. No wasted words.

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?

With one clearly documented parameter and an output schema present, the description covers all necessary context: what the tool returns, ordering significance, required parameter, and when to use it. It is fully sufficient for the agent to select and invoke this tool correctly.

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%, with board_id fully documented including source and error behavior. The description only repeats 'board_id is required,' which adds no new meaning. Baseline 3 is appropriate since the schema carries the parameter semantics.

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 opens with 'PRIMARY tool for board-column discovery' and explicitly states it 'returns every column of a Weeek board' with a clear return shape. This verb+resource combination clearly distinguishes it from sibling tools like weeek_list_boards or weeek_list_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?

The description provides explicit use-case guidance: 'Use when the agent needs a board's column/stage layout, e.g. to interpret a task's status or drive a board view.' It also labels itself as 'PRIMARY tool' for this purpose, implying precedence over alternatives, though it does not explicitly state when not to use it.

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