kaiten_list_boards

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. It only states that boards are listed, but it does not mention read-only behavior, pagination, the shape of the returned collection, or any other runtime characteristics. The word 'List' implies a read operation, but the description does not actively disclose these traits.

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 a single, front-loaded sentence that directly states the resource and scope. There is no verbose or repetitive content; every word contributes to understanding the operation.

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?

The tool is simple, but there is no output schema and no annotation support. The description plus the schema is enough to perform the basic call, but an agent lacks information about the response structure, pagination, and whether the returned boards include full or compact fields by default.

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%, so the schema already explains space_id and compact. The description adds little beyond reinforcing that the boards must be scoped to a space. This meets the baseline for a schema that fully documents its parameters without adding extra parameter nuance.

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 uses a specific verb ('List'), a concrete resource ('boards'), and a clear scope ('in a Kaiten space'). It naturally distinguishes itself from siblings like kaiten_get_board, kaiten_create_board, and kaiten_update_board by indicating a plural collection read operation.

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 context is clear: use this when you need to enumerate boards within a given space, with the required space_id serving as the scope identifier. It does not explicitly exclude situations where a single board should be retrieved via kaiten_get_board, so it falls short of full when/when-not guidance.

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