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

Annotations already mark this as a non-read-only, non-destructive, non-idempotent write, and the description adds genuinely new context: the required caller role and the cross-entity workspace constraint. It does not say what happens when an assignment already exists for that task/user pair, which matters given idempotentHint=false.

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?

Three short sentences, front-loaded with the core action, followed by permission and scope constraints. No filler or redundancy.

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?

With no output schema, full schema coverage, and annotations covering safety and idempotency, the description supplies the missing operational context (permissions, workspace scoping). The main gap is duplicate-assignment behavior and whether a success payload is returned.

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 100%, so all three parameters are already documented, including the role label and the hint to resolve userId via list_users. The description adds only the workspace-membership precondition, which is validation context rather than parameter semantics.

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: assigning a user to a task, with the optional role label clarified via an example. It doesn't distinguish itself from update_assignment or delete_assignment, so an agent must infer the create-vs-modify split from the name alone.

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 preconditions: an Administrator or ProjectManager role is required and both the task and user must belong to the active workspace. It stops short of naming alternatives such as update_assignment for changing an existing assignment's role.

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