update_canned_service_labor

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

No annotations are provided and the description does not disclose whether unspecified fields are preserved, whether this is a partial or full replacement update, or what the tool returns/does when the item does not exist.

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 concise sentence with no redundant words or filler.

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?

The tool is a simple mutation with well-documented parameters, but the description omits expected behavior for unspecified optional fields and return value, which would be useful given there is no output schema.

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?

All 8 parameters have individual schema descriptions, so the description adds little beyond the schema; it does not clarify relationships like how cannedServiceId and itemId interact beyond the field-level descriptions.

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?

Description clearly states the verb 'Update' and the specific resource 'a labor line item on a canned service template', which distinguishes it from sibling tools like add_canned_service_labor, remove_canned_service_labor, and update_canned_service.

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 this is for modifying an existing labor line item, but it does not explicitly state when to use it versus the add or remove labor-line siblings, or mention any preconditions.

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