reassign_tickets

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the dry-run default and what the non-destructive mode actually returns, which is exactly the kind of context an agent needs before a destructive bulk operation.

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?

Two short sentences, front-loaded with the operation and followed by the mode switch. The hard line breaks split single sentences awkwardly, but there is no filler content.

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?

An output schema exists, so return values need not be explained, and the dry-run behavior is well covered. However, for a destructive bulk mutation it omits what qualifies as an 'open ticket,' what happens to tickets beyond max_tickets, and whether elevated permissions are required.

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 0%, so the description must carry the burden, and it only elaborates on dry_run (default true, report-only behavior, how to execute). The three other parameters — from_user_id, to_user_id, and max_tickets — receive no explanation of meaning or constraints, leaving half the surface documented only by self-evident names.

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 states a specific verb and resource ('reassign an agent's open tickets to another agent'), making it immediately distinguishable from read-only siblings like find_tickets and agent_workload. It does not, however, explicitly contrast itself with adjacent mutation tools such as offboarding_report or set_user_status.

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 explains the two execution modes (report-only vs. execute) and their trigger, which is genuine usage guidance for the tool itself. It gives no guidance on when this tool is appropriate versus siblings that also touch ticket ownership, and no prerequisites or exclusions.

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