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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered, but the description adds genuine context: the per-card return shape, to-do task detail (done state, due date), sub-board recursion, permission flexibility, and the auth requirement ('Needs the user's Cotlet API key with access to this app'). It only lightly restates 'reads only', which the annotation already carries.

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?

The core purpose is front-loaded in the first sentence and each subsequent sentence adds usable detail. It runs a little long and mixes return-format, recursion, permission, and auth notes without strong grouping, so it is efficient but not maximally tight.

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 must explain the return value, and it does so well (one entry per card with type, text/URL, ID; to-do detail; sub-board entries). It omits pagination/volume behavior for large boards, which is the only notable gap for a read tool of this kind.

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 schema already documents both board_id and include_comments, establishing a baseline of 3. The description hints at board_id via the sub-board recursion note but adds no syntax or format detail beyond the schema, and never mentions include_comments.

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 states a specific verb+resource (get every card on a board) and enumerates the card types (notes, links, images, files, to-do lists, sub-boards), which cleanly distinguishes it from siblings like list_boards and search_boards. An agent can tell what the tool returns without opening the schema.

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?

It gives explicit recursion guidance ('Sub-boards appear as cards with their own board_id; call get_board again to open one') and clarifies permission scope ('works on boards you can view as well as edit'). It stops short of naming alternatives such as list_boards or search_boards, so the when-to-use routing is implied rather than explicit.

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