weeek_list_boards

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

With no annotations, the description must carry the full burden. 'List' implies a safe read, and it discloses the returned fields (id, name, privacy), which is useful. However, it says nothing about pagination, empty results, auth requirements, or rate limits, leaving behavioral gaps.

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, front-loaded with the resource and scope, then the routing hint. No filler text.

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?

No output schema exists, so it is good that the description names the returned fields. Combined with the single-parameter schema and the downstream-tool hint, the definition is nearly complete, lacking only pagination and error behavior detail.

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% and the single parameter is undocumented in the schema. The description compensates by explaining that 'project' accepts a name or id, which maps the string|number union to meaningful 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?

States a specific verb and resource ('List the boards of a WEEEK project') and even enumerates the returned fields (id, name, privacy). It differentiates implicitly by naming the downstream tools it feeds, though it does not directly contrast with siblings like weeek_list_projects or weeek_list_columns.

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 tells the agent the purpose context: 'Use it to find a board for weeek_move_task or weeek_list_columns.' This is clear when-to-use guidance with named alternatives, but there is no when-not or prerequisite information (e.g., permissions).

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