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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: a 100-board read cap with a boards_read counter (a silent-truncation risk the agent must know about), the traversal order (a board's lists top to bottom, then nested boards), and that due_time is only present when set. That is exactly the kind of behavioral disclosure annotations cannot carry.

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?

Front-loads the scope and return payload in the first sentence, then layers in traversal, limits, ordering, filtering and follow-up tools. Dense and nearly run-on in places, but every clause carries information an agent needs; nothing is filler.

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 describe returns — it does, field by field, plus the boards_read counter and conditional due_time. Combined with a fully covered input schema and explicit annotations, an agent has everything needed to call and interpret this tool correctly.

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 coverage is 100%, so the baseline is 3; the description still adds meaning by explaining that board_ids is a recursive walk including boards inside the given ones and that its default is Home, and by clarifying done's default of 'both'. It adds value but does not add syntax or format detail beyond the schema.

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+resource ('Every task in the to-do lists of your boards and the boards inside them') and enumerates exactly what each returned task contains (board, to-do list, text, done state, due date). It is clearly distinguishable from list_boards (boards only) and from add_task/set_task_done, which mutate rather than enumerate.

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 concrete usage context: default scope is Home, board_ids narrows it, and done filters open vs done. It also routes the agent forward to set_task_done, set_due_date and add_task using the returned board_id and card_id. It stops short of saying when NOT to use this (e.g. vs list_boards or search_boards), so it is strong context without explicit exclusions.

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