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

Annotations already declare that this is a non-read-only, non-idempotent, non-destructive, closed-world write, so the safety profile is covered. The description adds one genuinely new behavioral fact — that omitting the board falls back to the caller's active board — but says nothing about permission requirements, whether the assignee is notified, or what happens if the active board is missing. Note the description writes 'boardId' while the schema parameter is 'board_id', a minor naming mismatch rather than an annotation contradiction.

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 short sentences, front-loaded with the purpose and immediately followed by the routing rule; nothing is padded. The opening 'Use this to add a task' is slightly redundant with the tool name, keeping it from a 5.

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 an 11-parameter create tool with no output schema, the description is thin: it explains board routing but not subtask creation (parent_task_number/parent_board_id), status/priority behavior, assignee format, or what a successful call returns. Annotations carry the safety profile and the schema carries parameter details, so it is adequate, but the highest-risk behaviors are left to the schema alone.

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?

With 100% schema description coverage the baseline is 3, and the description exceeds it by documenting the default/routing semantics of the board parameter, which the schema only describes as 'Board ID where the task should be created.' It does not touch the other ten parameters, notably subtask creation via parent_task_number, so it does not earn a 5.

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 gives a specific verb+resource ('add a task'), which cleanly separates it from update_task and delete_task among the siblings. It stops short of naming an alternative or stating scope (e.g., single task per call, required title), so it is clear but not fully differentiating.

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?

'Provide boardId for deterministic routing; otherwise active board is used' tells the agent how to pick a board, which is real usage guidance for the most consequential parameter. However, there is no guidance on when to use this versus related tools (create_board, add_checklist_item, update_task) and no preconditions or exclusions.

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