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

Annotations already disclose the write profile (readOnlyHint=false, destructiveHint=true, idempotentHint=false, openWorldHint=true), so the bar is lower. The description does add one genuinely useful behavioral fact not in the schema: the card is placed in the Unsorted column with no column choice available. It says nothing about failure modes, permissions, or what is returned.

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?

A single front-loaded sentence with no filler; 'To-do list card' mildly echoes the title but the rest earns its place by specifying task contents and placement.

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?

With no output schema, the agent is left guessing whether the new card ID or URL is returned, which matters for follow-up operations like set_task_done. Given a fully documented 3-parameter schema and rich annotations, this is the main remaining gap.

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 text, due_date, due_time format, title default, and board_id sourcing. The description only restates that due date/time are optional and adds the implicit no-column-parameter fact, so baseline 3 applies.

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 names the concrete artifact being created (a to-do list card containing tasks with optional due date/time) and where it lands (Unsorted), which separates it from siblings like add_note, add_column, and add_comment. The verb is only implied by 'added to', so it is clear but not as crisp as an explicit 'Creates...'.

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?

There is no statement of when to choose this over alternatives such as add_note or add_column, and no preconditions surfaced (board must exist, board_id sourced from list_boards). Usage is only inferable from the resource type.

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