Sync Units Of Measure

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

The description adds partial update semantics beyond the annotations, which is useful. However, it does not explain the behavior of the `deletes` parameter, idempotency, or permissions. Given annotations are present, the added context is moderate.

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 clear and well-structured but includes some redundant information (e.g., full API path and category) that may not be necessary for an AI agent. The core information is presented upfront.

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 description covers the main operation and partial update but omits the `deletes` parameter behavior and detailed response structure. Since there is no output schema, this gap leaves the agent with incomplete information.

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?

Input schema has 100% description coverage, so the baseline is 3. The description only lists required parameters without adding meaning to the structure of `updates` or `deletes` arrays, which schema already provides.

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 clearly states the tool 'creates or updates a batch of Units of Measure' and specifies partial update behavior ('only the supplied fields are changed'). It distinguishes itself from sibling sync tools by naming the specific resource.

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 says 'Use this to update an existing Units of Measure records' but also claims it creates or updates. It does not provide explicit guidance on when to use this batch sync vs individual CRUD tools (e.g., create_unit_of_measure, update_unit_of_measure). A link to sync actions documentation is mentioned but not elaborated.

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