List Units Of Measure

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

The description adds behavioral context beyond the annotations: it specifies the return format (paginated JSON array with metadata), mentions pagination control, and identifies the endpoint. Annotations already declare readOnlyHint=true, so the description does not contradict but adds useful details.

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 four sentences, front-loaded with the main action and purpose. It achieves high information density without redundancy, covering usage, pagination, required params, and API reference efficiently.

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 purpose, usage, pagination, required params, and API reference. It explains the return format and metadata. For a simple list tool with robust schema and annotations, this is complete enough, though it could optionally mention default pagination values (already in 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?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining how to use page and per_page for pagination and that the response includes pagination metadata. It also reminds which parameter is required, providing practical usage guidance beyond the schema.

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 returns a list of all Units of Measure and enumerates use cases like paginated overview and finding IDs. However, it does not differentiate from sibling list tools for UOMs (e.g., list_unit_of_measure_categories), so it loses a point for lack of sibling differentiation.

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 provides clear guidance on when to use this tool (enumerate UOMs, paginated overview, find IDs, filter by query parameters) and mentions required parameters. It does not explicitly state when not to use it or name alternative tools, but the context is sufficient for a 4.

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