List Units

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but 'Get All' says nothing about read-only behavior, pagination defaults, filtering, ordering, or response characteristics. The agent cannot anticipate side effects or constraints.

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?

Two words is under-specification, not genuine conciseness. There is no front-loaded useful content or structured information beyond restating the tool's purpose.

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 list endpoint with 9 undocumented optional parameters, no annotations, and no parameter guidance, the description is completely inadequate. The presence of an output schema does not compensate for missing parameter and behavior semantics.

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 0%, and the description adds no meaning to any of the 9 parameters. An agent still cannot understand the purpose of page, search, orderBy, queryFilter, paginationSeed, or orderDirection.

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 'Get All' only restates the list semantics already implied by the name and title. It does not name the resource explicitly or distinguish list_units from other list tools like list_foods or the item-level get_units_by_item.

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 about when to use this tool instead of alternatives, no mention of pagination usage, and no exclusions. 'Get All' provides no routing or decision support.

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