wafeq_units_of_measure_create

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

The description adds meaningful behavioral context beyond the annotations: it explicitly says 'Not idempotent — calling twice creates two records' and explains how idempotency_key makes retries safe. This is consistent with the idempotentHint=false and readOnlyHint=false annotations, with no contradiction.

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 header is compact and informative, but the description repeats the same idea: 'Create unit of measure' and 'Endpoint for creating a new unit of measure' are redundant. It could be tighter without losing meaning.

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 endpoint, creation behavior, and idempotency, but there is no output schema and no mention of what a successful response returns. It also does not clarify the relationship to wafeq_item_units_of_measure_create, which leaves an ambiguity an agent might need to resolve.

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 schema already documents body fields and idempotency_key in detail. The tool description's mention of idempotency_key adds little beyond what the schema already states, and no additional parameter-level meaning is provided.

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: 'Create unit of measure' with endpoint POST /units-of-measure/. It is clear about the action but does not explicitly differentiate this from the sibling wafeq_item_units_of_measure_create, which is also a 'create' tool for units of measure.

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 no guidance on when to use this tool versus alternatives such as wafeq_item_units_of_measure_create or wafeq_units_of_measure_update. It only states that it creates a unit of measure, leaving the selection logic largely to inference.

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