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 fully covered. Beyond that, the description discloses the exact payload a caller receives (description, checklist, links, watchers, estimate, column), which is meaningful since there is no output schema.

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 first front-loads scope and return content, the second resolves the addressing question. Nothing repeats the name or title.

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 3-parameter read tool with no output schema, the description supplies the missing knowledge about what is returned and how the card is identified. The required project_id is left to the schema, which is acceptable given its explicit description.

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 basline is 3. The sentence 'Address it either by card_id or by its human key like OPUS-451' adds a concrete key example, but the either/or exclusivity is already stated in the schema's own parameter descriptions, so it adds little beyond what is structured.

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 (read) and resource (one kanban card) and immediately enumerates what the card contains: description, checklist, links, watchers, estimate, column. The emphasis on 'ONE card in full' distinguishes it from the list/search siblings (search_kanban_cards, get_kanban_board, get_my_kanban_tasks) without needing to name them.

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 how to address the card (card_id or human key), but gives no guidance on when to use this tool versus search_kanban_cards for lookup or get_kanban_board for the whole board. The 'ONE card in full' phrasing implies single-card retrieval but never states the condition or exclusions.

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