Get Units Of Measure

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

Annotations already indicate readOnlyHint, destructiveHint, etc. The description adds pagination and scope context but also introduces confusion by suggesting the tool returns incidents, which misrepresents behavior. No contradiction with annotations, but the mixed messaging reduces transparency.

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 but contains an irrelevant and misleading sentence about fetching incidents, which undermines conciseness and clarity.

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 provides some return structure (display label, server value) and pagination details, but the contradictory statements about incidents make it incomplete and unreliable for an agent.

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?

Input schema has 100% coverage, so baseline is 3. The description merely repeats that company_id is required and mentions page/per_page, adding no new semantic value beyond schema definitions.

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 initially states it returns units of measure for incident environmental records, but later incorrectly says it fetches 'full details of a specific Incidents by its identifier' and 'Returns a paginated JSON array of Incidents.' This contradiction obscures the true purpose of listing 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?

No guidance is provided on when to use this tool versus sibling tools like list_units_of_measure or show_unit_of_measure. The description does not differentiate usage context or offer alternatives.

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