Show Unit Of Measure

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

Annotations already indicate readOnlyHint=true and idempotentHint=true. The description adds that it returns a JSON object and references the API endpoint, but does not disclose behavioral aspects like rate limits or pagination behavior (page/per_page parameters exist in schema). Adequate but not enhanced beyond 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 concise with three sentences. It front-loads the purpose and includes necessary details (return type, required params, API info) without unnecessary verbosity.

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 read-only retrieval tool with comprehensive annotations and schema, the description covers the essential details. It lacks specifics about the response structure (though no output schema exists), but the API endpoint hint compensates. Good but could mention typical response fields.

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% with clear parameter descriptions. The description only repeats required parameters (company_id, id), adding no new meaning or context. Baseline score of 3 is appropriate.

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 fetches details of a specific Unit of Measure by identifier. It distinguishes from sibling tools like 'list_units_of_measure' (list all) and 'sync_units_of_measure' (sync). The verb 'show' and resource 'Unit of Measure' are specific and unambiguous.

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 explicitly says to use this tool to fetch full details of a specific UOM by identifier. However, it does not mention when not to use it or provide explicit alternatives. Nevertheless, the context of sibling tools and the clear use case make it effective.

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