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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=false, covering the safety profile. The description adds that the call 'Returns the updated board' and that it targets one of the user's boards, but says nothing about permissions, duplicate handling, or what happens if the named board/column doesn't exist.

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 sentences, zero waste, and the usage condition is front-loaded before the sibling alternative. Nothing is repeated from the schema or annotations.

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?

An output schema exists, so explaining return values is optional and the brief 'Returns the updated board' suffices. For a 6-parameter mutation tool the definition covers purpose, trigger, and the named alternative, but omits semantics for the remaining undocumented parameters, which keeps it short of complete.

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 67%, so most parameters are documented in the schema itself. The description reinforces column and due-date behavior ('optionally in a named column with a due date') but never addresses assignToMe or the description parameter, leaving two of six fields without any added meaning.

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 ('add a task or card'), names the target container (Xenition boards), and distinguishes itself from create_board, which handles whole-board creation. An agent can pick this over siblings like create_board or move_task without opening a 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 an explicit trigger ('Use this when the user wants to add a task or card') and names the alternative create_board with the condition that selects it. It does not mention related siblings such as move_task, complete_task, or list_tasks, so the routing guidance is good but not exhaustive.

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