doordash_store_menu

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

With no annotations provided, the description carries the transparency burden. It discloses that no authentication is required, that the menu is location-aware, and describes the response structure. It lacks details on errors or rate limits, but covers the key behavioral aspects for a read-only fetch.

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, front-loaded with the primary purpose, and no filler. Every clause adds useful information about output or authentication.

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 menu-fetching tool with no output schema, the description explains the return content (sections, item names, descriptions, prices) and the auth context. It could mention failure modes or whether item IDs are included for follow-up calls, but overall it is sufficiently complete for typical use.

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%, with each parameter described (store_id, latitude, longitude). The description adds context that the menu is location-aware, tying latitude/longitude to behavior, but does not add further format or constraint details 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 and resource: 'Get a DoorDash store menu.' It clearly states what is returned (menu grouped into sections with item names, descriptions, and displayed prices), distinguishing it from sibling tools like doordash_store or doordash_store_item.

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 gives clear context: this returns a location-aware menu and requires no DoorDash account or token. It does not explicitly name alternatives or exclusions, but the purpose is specific enough for an agent to choose it for menu retrieval.

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