weeek_list_board_columns

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

No annotations provided, so description carries full burden. Discloses return format as array of {id, name, boardId, order}. Notes that default limit of 20 protects against MCP response cap, indicating rate awareness. Could explicitly state read-only nature, but sufficiently safe implied.

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?

Three sentences with zero fluff. First sentence states purpose, second covers usage order and return format, third clarifies parameter source. Every sentence earns its place.

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?

Despite no annotations or output schema, description provides purpose, usage ordering, parameter constraints, return structure, and rationales. Covers all essential information for an agent to correctly select and invoke the 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?

Schema documentation covers all 3 parameters. Description adds value: explains board_id must be obtained from weeek_list_boards and warns against guessing. Also contextualizes default limit as protection against token cap. This extra guidance elevates above baseline 3.

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 describes the tool as listing columns (status buckets) of a specific WEEEK board. Defines verb, resource, and clarifies columns as task status mechanism. Differentiates from sibling tools by specifying use after weeek_list_boards and before weeek_move_task.

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 states when to use: 'Use this AFTER weeek_list_boards' and 'MUST call this before weeek_move_task (Phase 3)'. Also warns that board_id must come from weeek_list_boards and not to guess, providing clear sequencing and prerequisites.

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