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

Annotations already mark the operation as readOnly and non-destructive, and the description adds strong behavioral detail: output shape, sorting order, key fields, and the opaque `content` JSON string. It does not repeat the annotation flags but complements them with return semantics, earning a high score.

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 sentences, front-loaded with the core purpose, followed by output details and a usage hint. Every sentence earns its place and uses inline code for clarity. No fluff or redundant phrasing.

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 burden of explaining the return value, which it does thoroughly: structure, ordering, fields, and the opaque content string. For a read-only list operation with a rich return contract, this is complete and actionable.

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?

The schema documents `access_key` well, and the description adds context about the board being a 'todo' board, but it does not elaborate on `board_id` beyond the obvious. Since schema coverage is 50% and the description focuses on output rather than parameter details, it is adequate but not outstanding.

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?

The description uses a specific verb ('Read'), names the exact resource ('full kanban state of a todo board'), and details the output structure (`{ mode, columns, tasks }`) with ordering by sort key. It clearly differentiates this tool from siblings by emphasizing it returns the full state and exact ids for later mutations.

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 explicitly states when to use the tool ('Use this to get exact column/task ids before updating, moving or deleting'), giving clear usage context. It implies that other operations requiring ids should be preceded by this tool, distinguishing it from query or update variants.

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