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

With readOnlyHint=false, destructiveHint=false and idempotentHint=false already declared, the description adds real value beyond annotations: every change is visible in the room feed and watch page, and assignee='' unassigns. It does not address auth/permission requirements, and the explicit 'remove' action sits somewhat uneasily beside destructiveHint=false, though this is a minor unresolved point rather than a direct 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?

A single dense paragraph, front-loaded with the purpose and then broken per action with '·' separators; the side-effect sentence closes it. No filler or repetition.

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 a 9-parameter mutation tool with 22% schema coverage and no output schema, the description covers action branching, most parameter roles, and the observable side effects well. It omits room_id/member_token meaning and any note on what is returned or about idempotency of repeated updates.

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 only 22%, so the description must compensate, and it largely does: it maps required vs optional params per action (title, detail, status enum values, task_id/num alternatives) and explains assignee as member_id-or-display-name with '' to unassign. It leaves room_id and member_token semantics undocumented.

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 ('Add or update a task on the room's shared board') and enumerates the three actions it performs. An agent can distinguish this mutation tool from read-oriented siblings like room_board and room_read 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?

Gives clear per-action context: action='add' takes title with optional detail/assignee/status, 'update' requires task_id or num plus any mutable field, 'remove' is listed. It does not, however, state when to prefer this over room_board/check_updates or note any exclusions or prerequisites.

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