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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the view updates live during the conversation, the user can mutate it (drag, complete, add), and incapable clients receive the same board as JSON. That interaction model is not derivable from the 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?

Three compact sentences, front-loaded with the core purpose, followed by the default-selection rule and the JSON fallback. No filler and nothing repeated from the schema or annotations.

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?

There is no output schema, so the description carries the return-value burden and does so by explaining both the interactive rendering and the JSON fallback. Combined with full parameter documentation and read-only annotations, an agent has nearly everything needed, though it lacks explicit routing advice against sibling read tools.

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% and there is a single optional parameter, so the schema already documents boardId and its default. The description's 'Without boardId it shows the board the user changed most recently' merely restates the schema default rather than adding syntax, format, or selection guidance.

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 ('Shows a board') and goes further by describing the rendering mode: an interactive live-updating kanban with lists, cards, labels, due dates and assignees. This meaningfully distinguishes it from the data-oriented sibling get_board, though it never names that sibling explicitly, so differentiation is implied rather than stated.

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 description explains the no-argument default ('the board the user changed most recently') and a client-capability fallback, but gives no explicit when-to-use guidance relative to siblings like get_board, list_boards, or overview. The agent must infer that this is the display-oriented tool rather than the data-retrieval one.

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