doordash_store_item

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

With no annotations provided, the description carries the full burden. It discloses that no DoorDash account or token is required, which is a notable behavioral trait. However, it does not mention the return format, potential side effects, rate limits, or why latitude/longitude are needed beyond the schema. This is adequate but not rich.

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 three short sentences, front-loaded with the primary action, and every sentence adds value: purpose, source scope, and auth requirement. There is no redundancy or filler.

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 simple read tool with 4 required parameters and no output schema, the description is mostly adequate. It covers the purpose and auth, but lacks details on what 'details' include and doesn't specify expected response content. The schema covers parameter meanings, so the main gap is return value expectations.

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 baseline is 3. The description adds no additional meaning beyond the schema; it doesn't explain the relationship between parameters or provide usage examples. Thus it does not improve on the structured data.

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 DoorDash menu item details' with a specific verb and resource, and distinguishes it from sibling tools like doordash_store_menu and doordash_search by focusing on a single item. It also identifies the data source ('Android mobile guest experience'), making the purpose unambiguous.

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 usage for retrieving a specific menu item's details based on the presence of item_id and store_id, and notes that no auth token is required. However, it does not explicitly state when to use this tool instead of alternatives like doordash_store_menu or doordash_search, nor does it provide exclusionary guidance.

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