add_assignee

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the mutation itself; it does not say whether assignment is additive, whether an existing assignee is replaced, whether multiple assignees are allowed, or what validation/permission requirements exist.

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, front-loaded sentence with no filler; every word contributes to the core action. For a two-parameter tool this is an appropriately sized statement of purpose.

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 simple two-parameter write operation, the description is minimally sufficient to construct a call: task_id identifies the task and user_id identifies the user. However, it is incomplete on behavioral context (add vs. replace, duplicates, permissions) and does not mention the sibling remove_assignee/list_assignees for contrast, leaving room for hesitation.

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 0% and the schema only provides names/titles. The description maps 'user' and 'task' to the two parameters only implicitly and gives no operational details such as ID validity, uniqueness, or relationship to existing assignees, so it doesn't compensate for the missing parameter descriptions.

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 action ('assign') and the objects ('a user', 'a task'), so the core purpose is unambiguous and semantically distinct from remove_assignee/list_assignees. It doesn't explicitly name or differentiate siblings, so it falls short of a 5.

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?

No guidance is given on when to use this tool instead of alternatives, nor any context about prerequisites, exclusions, or ordering relative to other operations. The description implies the obvious use case but provides no explicit usage direction.

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