kaiten_get_board

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description usefully adds that the response is an aggregate (board + columns + lanes + property config), but says nothing about auth requirements or payload size/pagination.

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?

A single eleven-word sentence with no filler, and the resource is front-loaded before the payload enumeration. Nothing to trim.

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?

For a simple single-parameter getter with a full output schema, the description is nearly sufficient — the return values are covered by the output schema and summarized in the text. Only the missing board_id provenance keeps it from being complete.

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?

One required integer board_id with 0% schema description coverage, and the description offers no format, sourcing, or validity guidance for it. The parameter is self-evident from its name and type, so the baseline of 3 applies rather than a penalty.

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?

Specific verb (Get) plus resource (board) and an enumeration of the payload it returns: details, columns, lanes, and custom property configuration. This separates it from kaiten_list_boards, though it never explicitly contrasts itself with the standalone kaiten_list_columns/kaiten_list_lanes siblings.

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?

No when-to-use guidance at all: nothing says to call this after kaiten_list_boards to resolve a board_id, and no exclusion versus list_columns, list_lanes, or get_space. The agent must infer usage entirely from the name.

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