Get Board

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds useful behavior beyond the schema: the max verbosity inlines columns and lanes, making redundant sibling calls unnecessary. No contradiction with annotations.

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 sentences with no filler. The core operation is front-loaded, followed by the high-value verbosity tip and boardId provenance. Every phrase 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?

The tool is simple, has only two parameters, and benefits from rich annotations. The description covers what the tool returns at a high level, explains the key verbosity behavior, and provides ID provenance. Since there is no output schema, slightly more detail about the metadata fields returned could be helpful, but it is not necessary for correct invocation.

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 100%, so the baseline is 3. The description adds real value by explaining the practical effect of verbosity=max, which the schema enum alone does not convey. It also reinforces where boardId is obtained, though that duplicates the schema description.

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: 'Get board metadata.' It further clarifies scope by noting that verbosity=max returns inline columns and lanes, distinguishing it from list-only and card-related siblings without needing to open their schemas.

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?

Provides concrete usage guidance: for a board overview, verbosity=max can replace separate kaiten_list_columns / kaiten_list_lanes calls. It also tells the agent where boardId comes from. It does not explicitly say when not to use this for card retrieval, but the 'metadata' scope makes that distinction reasonably clear.

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