get_item_price

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

No annotations provided, so description carries full burden. It discloses read behavior and exact match semantics, plus a caveat about empty results. Lacks details on permissions or response format, but output schema covers return values. Good transparency for a simple read tool.

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?

Extremely concise: two sentences plus a warning. Front-loaded with purpose and immediate usage context. No redundant words, every sentence adds value.

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?

Given the presence of an output schema and high schema coverage, the description is nearly complete for a simple item price lookup. Includes a useful caveat about empty results. Minor omission: no explicit mention that it only returns a single record or multiple, but schema and name imply list. Overall sufficient.

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 100%, so schema already documents both parameters adequately. Description adds no extra semantic value beyond the schema, as the exact match and optional price list are already defined. 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?

Description clearly states 'Get item prices from Item Price records' with specific resource and verb. Emphasizes exact match on item_code, distinguishing it from fuzzy search tools like find_items. Leaves no ambiguity about what the tool does.

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?

Explicitly warns that exact match may return empty results and suggests using find_items if item_code is uncertain. This provides clear when-to-use and when-not-to-use guidance, directly aiding agent decision-making.

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