Get prices

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

The description adds valuable context beyond the annotations: it specifies the exact return format and notes that price may be a number or string, requiring decimal handling. Annotations already declare readOnlyHint/idempotentHint/destructiveHint, so the description's added behavioral details earn a solid score.

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 sentences, no fluff. The first sentence states the purpose and endpoint; the second gives the return structure and a crucial type caveat. Every word earns 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?

Despite no output schema, the description provides the full return format and a type caveat. Combined with the schema (parameter description) and annotations (safety profile), it gives an agent enough to use the tool correctly. Could mention limitations (e.g., max price list count) but not essential.

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?

The only parameter (pricelist_ids) is fully described in the schema as 'Price-list ids from query_price_lists.' The description does not add any meaning beyond that, so it matches the baseline 3 for high schema coverage. No new parameter semantics are introduced.

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's function: retrieving product prices for one or more price lists. It includes the endpoint (POST /b2b/v1/prices/get) and return shape, making it specific and distinct from sibling tools like query_price_lists (lists price lists) and set_prices (writes prices).

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?

Usage is implied by the phrase 'for one or more price lists' — the tool is used when you need prices for specific price lists. However, there is no explicit guidance on when to use it over alternatives, no exclusion criteria, and no mention of when not to use it.

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