instacart_item

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

The description adds 'Public data sourced from Instacart's own storefront pages,' which informs the agent about the data source and public nature. It also enumerates the returned attributes. However, with no annotations and no output schema, it does not disclose limitations or behaviors like geolocation dependence beyond what the schema describes.

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 concise, front-loaded with the main purpose, and the second sentence efficiently lists the return fields and data source. Every sentence adds value without redundancy.

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 covers the return fields and data source, which is adequate for a detail-lookup tool. The schema descriptions handle the provenance of identifier parameters. It doesn't explicitly tie into a workflow with sibling tools, but that is not necessary given the schema covers it.

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 coverage is 100% and each parameter already includes a description (e.g., shop_id from GET /instacart/stores). The tool description adds little beyond the schema, only emphasizing 'at a specific store.' This meets the baseline for high schema coverage.

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 'Get Instacart product detail at a store' with a specific verb and resource. It lists the returned fields (name, size, brand, image, pricing, availability, etc.), distinguishing it from sibling tools like instacart_search or instacart_stores.

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 implies this tool is used for looking up a single product's detail at a specific store, and mentions it's public data. However, it does not explicitly state when to use it versus alternatives (e.g., instacart_search for finding products) or provide exclusion criteria.

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