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

Annotations only cover idempotency and non-destructiveness; the description adds real behavioral context beyond that — the user assignee is silently removed when reassigning to another team, the customer is not e-mailed, and the assigned agent may be notified. It also discloses the underlying endpoints, so the agent understands the exact 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?

Three tight sentences with the mutation class front-loaded and the XOR rule stated before the edge cases. The trailing 'POST /tickets/{id}/...' endpoint detail is implementation-level and adds little for an agent, costing a point.

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 3-parameter write tool with no output schema, it covers targets, side effects, notifications, and the team-membership prerequisite. It does not mention what a failed assignment returns (e.g., a non-member user) or the response shape, though that is a minor gap.

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 the baseline is 3, but the description goes further by defining the mutual exclusivity of user_id/team_id (a constraint the schema does not encode) and the rule that a team assignee must already be a member. It stops short of stating that ticket_id is mandatory and that omitting both targets fails.

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?

It names a specific verb (assigns) and resource (ticket) and immediately states the two mutually exclusive targets (user_id XOR team_id). 'WRITE:' front-loads the mutation class, making it clearly distinct from sibling supportbee_unassign_ticket and the read 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?

It gives explicit routing context: choose exactly one of user_id or team_id, and only a team member can receive a team-owned ticket. It does not, however, explicitly name when to prefer this over supportbee_unassign_ticket or the conditions under which assignment should be skipped.

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