manage_work_item_assignee

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals important traits: removal is applied before addition when both are provided, and already-assigned users are silently skipped. This adds meaningful context beyond the basic operation. However, it omits potential error conditions, permission requirements, or side effects, so a perfect score is not warranted.

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 well-organized and compact. The main behavior is stated in one sentence, followed by operational details and a clear Args/Returns structure. Every sentence adds value, and there is no redundant information.

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?

Given the tool's moderate complexity, the description is complete: it explains the core behavior, parameter semantics, order of operations, silent skipping, and return type (Updated WorkItem object). The presence of an output schema further reduces the need to describe return structure in detail. No critical context is missing.

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 0%, so the description must compensate. The 'Args:' section clearly defines each parameter (project_id, work_item_id, add_user_id, remove_user_id) and their roles. It also explains the interplay between add and remove parameters. This is solid compensation, though it could go further by addressing edge cases like passing neither add nor remove.

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 clearly states the tool's function: 'Add or remove a single assignee on a work item without replacing the full list.' It identifies the specific verb (add/remove), the resource (work item assignee), and the key scope (single assignment, not full list replacement), which distinguishes it from broader update tools.

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 clear context for use, emphasizing 'without replacing the full list' to differentiate from batch assignment operations. It also explains the usage pattern ('Provide add_user_id, remove_user_id, or both') and the order of operations. However, it does not explicitly name alternative tools or state when not to use this tool, so it falls short of a 5.

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