ftrack_assign_user_to_task

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

With no annotations, the description carries the full responsibility for behavioral disclosure. It only says 'Assign a user to a task' without explaining whether existing assignments are overwritten, required permissions, or failure modes. This leaves the agent blind to side effects.

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 terse sentence, front-loaded with the core action. However, it is under-specified for a mutation tool, lacking even basic guidance. While not verbose, it does not achieve the 'appropriate size' needed to be truly helpful.

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 simple two-parameter nature, the description is minimal but insufficient. With no annotations or output schema, it fails to clarify side effects, return values, error handling, or whether the assignment replaces existing users, leaving the agent under-informed for correct invocation.

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 both parameters with 100% coverage, providing clear descriptions for task_id and user_id. The description adds no additional meaning, but the schema already does the heavy lifting, so the baseline of 3 is appropriate.

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 resource 'user to task', which identifies the tool's purpose. However, it does not differentiate from sibling tools like list_user_assignments or ftrack_update_task_status, lacking any scope or nuance.

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?

There is no guidance about when to use this tool versus alternatives, no prerequisites, and no mention of how assignment relates to other task operations. The description provides no context for decision-making.

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