Assign ticket

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

Annotations indicate a non-read-only, non-destructive operation. The description adds the behavioral nuance of unassignment by omitting user_id, which is not fully captured by annotations alone. It also implies the assignee must be a staff user, adding useful context beyond the schema.

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 redundant words. Every part contributes meaning, and the parenthetical reference to list_users is efficient.

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 tool with no output schema, the description covers the purpose, the main behavioral variant, and a pointer to related tooling. It slightly lacks explicit error handling or permission context, but these are not critical for a tool of this complexity.

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 100%, so the baseline is 3. The description adds value by specifying that the user must be a staff user and referencing list_users for obtaining valid IDs, which enriches the meaning of user_id beyond the schema's 'Omit to unassign'.

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 uses a specific verb ('assign') and identifies the resource ('ticket') and target ('staff user'), clearly distinguishing it from generic update tools. It also explicitly states the unassign behavior, which differentiates it from other ticket operations.

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: use to assign a ticket to a staff user, with a pointer to list_users for finding valid users. It does not explicitly mention when not to use it, such as choosing update_ticket for other ticket changes, but the context is adequate for a simple tool.

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