ingrammicro_get_price_and_availability

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds useful context about real-time data and pre-order usage, but does not disclose additional behavioral details such as constraints, warehouse-related behavior, or response semantics beyond what the output schema and parameter descriptions already provide.

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 a single, focused sentence with the core action front-loaded and the business context following afterward. There is no redundant wording or repetition of schema details.

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 fully documented input schema, an output schema, and annotations covering safety and idempotency, the description provides the missing business context: this is the pre-order verification step. Nothing essential is left unexplained for an agent to select and invoke the tool correctly.

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 the input schema already explains the products, include_pricing, include_availability, availability_by_warehouse, and include_product_attributes parameters. The description only paraphrases the high-level purpose ('price and/or stock availability' and 'one or more SKUs') without adding meaning beyond the schema.

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 uses a specific verb ('Get'), a clear resource (real-time price and/or stock availability), and scopes the operation to one or more SKUs. It also distinguishes itself from order creation by explicitly positioning this as the pre-order check before calling ingrammicro_create_order.

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 clearly states when to use it: before placing an order, to confirm current price and stock. It names the downstream sibling (ingrammicro_create_order), though it does not explicitly discuss when not to use it or compare it with search/products/detail alternatives.

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