wafeq_item_units_of_measure_create

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

Beyond the annotations' idempotentHint=false, the description explicitly warns that calling twice creates two records and explains how idempotency_key makes retries safe. It also flags the operation as WRITE/creates data, giving an agent a concrete behavioral model. No contradiction with annotations.

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 short and front-loaded, with a useful header line containing the operation type and endpoint. However, 'Create item unit of measure' and 'Endpoint for creating a new item unit of measure' are redundant, so it is not perfectly polished.

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?

For a create endpoint with a fully described schema and good annotations, the description provides the needed core context: what is created, via which endpoint, and how to handle retries safely. It does not describe relationships to existing items/units, but the schema fields cover the data contract.

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 the body and idempotency_key thoroughly. The description's idempotency note restates what the idempotency_key parameter description already says, adding no new parameter semantics. Baseline 3 applies.

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 ('Create') and resource ('Item Unit Of Measures'), backed by the exact POST endpoint. This clearly differentiates the create operation from sibling list/retrieve/update/destroy tools on the same resource, even if it does not explicitly contrast with units_of_measure_create.

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 makes the tool's purpose obvious ('Endpoint for creating a new item unit of measure') but does not explicitly state when to choose it over alternatives or exclude other operations. The idempotency guidance is useful for retries, but it is parameter-level guidance rather than tool-selection guidance.

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