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

Goes well beyond the annotations (readOnly=false, destructive=true, openWorld=true) by disclosing the concrete side effect: a push and email are sent to the assigned member, mirroring in-app behavior. It also explains the confirm/preview mechanic and the self-assign/unassign exception, giving the agent a precise picture of consequences before acting.

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 that lead with the core action and then layer the important behavioral conditions. The second sentence is dense and slightly run-on with multiple clauses, but no sentence is wasted.

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 destructive, open-world mutation with no output schema, the description covers the key concerns: side effects, the confirm requirement, and preview behavior. It is missing the value format for add/remove and any permissions/error context, but the essential call-time knowledge is present.

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 low (25%), so the description carries weight, and it does clarify the confirm parameter's semantics (redundant with the schema description) plus the add/remove intent via 'assigns or unassigns.' However, it never specifies what add/remove actually contain (member identifiers, array format) or the meaning of cardId, leaving part of the gap unfilled.

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: 'Assigns or unassigns board members on a task.' This is clearly distinguishable from siblings like set_task_labels or set_task_field by resource. It stops short of explicitly contrasting with a named alternative, so it lands just below the top mark.

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 conditional usage guidance: when assigning someone other than the user, confirm:true is required and omitting it yields a preview; self-assigning and unassigning are exempt. This is clear context for how to invoke it correctly, though it doesn't name alternative tools for related operations.

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