update_task_assignment

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

Annotations indicate modification, non-destructive, and idempotent. The description adds context on special values ('me', 'null') but does not contradict annotations. It provides useful but not extensive behavioral detail.

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 sentences, front-loaded with main purpose, no waste. Every sentence adds value, including the special handling notes.

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 update with two parameters, no output schema, and annotations covering safety, the description is complete. It covers all necessary special cases.

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 baseline is 3. The description adds meaning beyond the schema by explaining the 'me' and 'null' usage for assignee_id, which compensates well.

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 updates the assignee of an existing task, with specific verb and resource. It distinguishes from siblings by focusing on assignment and providing special cases like 'me' and 'null'.

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 implies when to use the tool (to change assignee, including unassigning) but does not explicitly mention alternatives or when not to use it. However, the context of sibling tools makes it clear.

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