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

Annotations establish readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is already covered. The description adds genuinely new behavioral context beyond the annotations: 'The person is notified,' which is a side effect an agent should anticipate, plus confirmation that clearing is a supported mode.

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 with zero filler, front-loading the primary action before the secondary clearing mode. Every clause earns its place.

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 simple three-parameter mutation with no output schema, the description covers both operation modes and the notification side effect. It stops short of noting permission requirements or whether re-assignment overwrites silently, which would round it out.

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 all three parameters, including that assignee_id is omitted to clear and where to source it (list_kanban_members). The description adds nothing beyond what the schema states, so the baseline 3 is appropriate.

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 and resource ('Assign a card') and covers the inverse operation ('clear the assignee'). It is distinguishable from update_kanban_card, though it never names that sibling explicitly, so the differentiation is implicit rather than stated.

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?

The phrase 'or clear the assignee' implies the second mode of use, and the schema notes that omitting assignee_id clears it. However, there is no guidance on when to prefer this over update_kanban_card or move_kanban_card, and no exclusions.

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