assign_technician

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

With no annotations, the description carries the full burden for behavioral disclosure. It states the assignment action but does not mention whether an existing assignment will be replaced, what happens on invalid IDs, or any response/return behavior.

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 two sentences and contains no redundant or extraneous information. The workflow guidance is compact and directly relevant.

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?

It includes necessary prerequisite lookup steps and correctly identifies all required inputs. It lacks explicit postcondition or output information, but given the simplicity of the action, it is reasonably complete.

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 schema provides basic descriptions for all three parameters, and the tool description adds useful context by explaining how to obtain orderId, laborIds, and technicianId through related tools. This goes beyond the schema but does not deeply detail each parameter.

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 clearly identifies the resource ('technician') and target ('one or more labor line items on a work order'). It is distinct from sibling tools like add_service_to_order and list_labor.

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 explicitly tells the agent which lookup tools to use for each input parameter (list_services, list_labor, list_users), providing a clear workflow before calling this tool.

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