wafeq_item_units_of_measure_list

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description mostly repeats this with 'READ-ONLY' and adds no new behavioral facts such as default pagination, maximum page size, ordering, or filtering 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 short and the READ-ONLY/endpoint line is front-loaded, but it is repetitive: 'List item unit of measures' and 'Endpoint for retrieving a list of item unit of measures' convey the same information twice. Every line does not earn its place.

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 simple read-only list endpoint with two optional pagination parameters, the annotations plus schema are sufficient to invoke it correctly. The only notable gap is not distinguishing this from the similarly named wafeq_units_of_measure_list, but that is not required for basic invocation.

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%, and both page and page_size already have clear descriptions. The tool description adds no parameter-level meaning, so the baseline of 3 is appropriate; the schema does the heavy lifting.

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 a specific verb and resource: 'List item unit of measures' and identifies the exact endpoint GET /item-units-of-measure/. The list semantics separate it from the sibling create, retrieve, update, and destroy tools for the same resource, so an agent can tell them apart without opening schemas.

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?

There is no guidance on when to select this list endpoint instead of alternatives such as wafeq_item_units_of_measure_retrieve or wafeq_units_of_measure_list. No exclusions, prerequisites, or use-case hints are provided beyond the implied 'if you need a list' reading of the name.

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