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

Adds substantial context beyond the annotations: required permission (task.assign on the project), target precondition (active org member), the CONFLICT failure mode for expectedAssigneeRevision, and the returned claimRevision that enables chained optimistic-concurrency assigns. With destructiveHint=true already declared, this level of precondition and error disclosure is more than the annotations carry on their own.

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?

Front-loads the core action and the unassign idiom, then layers concurrency and capacity detail in a logical order. It is a single dense paragraph running well over a hundred words, and the `load` payload sentence could be tightened, but every sentence carries information the agent can act on.

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?

There is no output schema, and the description compensates by documenting the return shape (assignee id and name, claimRevision, and the capacity/load block including over, overBy and otherWork). It also covers permissions, target preconditions, error semantics and dryRun pairing, leaving no material gap for a five-parameter mutation.

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 five parameters and the baseline would be 3. The description nonetheless adds operational meaning the schema states only tersely: why email resolution exists, how expectedAssigneeRevision fails and how claimRevision is meant to be reused for chaining.

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 or unassign one task') and immediately delimits scope to a single task, which distinguishes it from the sibling bulk_assign. The unassign path is described in the same breath, so the agent knows this tool covers both directions.

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 explicit guidance on when to reach for assigneeEmail versus assigneeId, including the rationale ('when the agent only knows the user's email and would otherwise need a separate list'), and states the two are mutually exclusive. It does not, however, name tool-level alternatives such as bulk_assign or propose_assignment, so routing between sibling tools is left to inference.

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