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

Annotations already indicate this is a non-read-only, non-idempotent, non-destructive write operation. The description adds the unassign behavior and role restriction, but it doesn't disclose side effects such as whether an existing assignee is replaced or what happens if the request is already assigned.

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?

The description is a single sentence that efficiently captures the action, the unassign mechanism, and the permission restriction. There is no filler or redundant restatement of the tool name.

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 four-parameter mutation with no output schema, the description covers the essential call semantics: what the tool does, how to unassign, and who is allowed to use it. It doesn't explain state assumptions or return behavior, but the schema already documents all required parameters, making the description sufficient for a straightforward assignment operation.

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?

The input schema covers all four parameters with descriptions, so the schema is doing the heavy lifting. The description adds little parameter-level meaning beyond the schema; the user_id: null unassign behavior is already stated in the schema itself.

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?

The description states a precise action: assign (or unassign) a team member to fulfil an extra-capture request. The verb and resource are clear and specific. It doesn't explicitly contrast with sibling assign tools like assignClarityLandscapeCaptureRequest, but the resource naming is distinct enough.

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 description gives concrete usage clues: pass user_id: null to unassign, and the tool is restricted to Lead Builders and above. However, it doesn't explain when this tool should be chosen over sibling assignment tools or provide exclusions, so the agent must infer selection from the name.

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