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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond them: the response is deliberately partial (card descriptions omitted) and the brief must be read before touching cards. It stops short of disclosing volume limits, pagination, or whether archived cards are included.

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, zero filler. The return contents are front-loaded and the omission/routing guidance is compressed into a parenthetical and a follow-on clause rather than sprawling.

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?

An output schema exists, so return-value shape need not be explained, yet the description still summarizes scope precisely. For a single-parameter read tool with full annotation coverage, nothing needed to invoke it correctly is missing.

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?

There is a single parameter with 100% schema coverage ("the project UUID to load"), so the schema already carries the semantics. The description adds no syntax, format or scoping detail about project_id, leaving the baseline 3.

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 a Kanban board") and enumerates exactly what is returned: columns, brief, and every card with a defined metadata set. It distinguishes itself from get_card and get_card_detail by explicitly naming what it omits (card descriptions) and pointing to those 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?

Gives an explicit precondition for the brief ("read it before working on the board's cards") and routes the agent to specific alternatives with the condition that selects them: get_card for the body, get_card_detail for body plus comments, events, checklist and attachments in one call. This is a clear when-to-use-which decision rule.

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