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

Beyond the readOnlyHint/openWorldHint annotations, it discloses non-obvious behavior: itemId is matched case-insensitively by name, no stable per-item identifier exists, unmatched names return not-found, and no substitute is returned. It also states no auth is required. This is exactly the behavioral context an agent needs before invoking.

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?

Four compact sentences, purpose front-loaded, then matching semantics, failure behavior, and requirements. The closing sentence partly restates required fields already in the schema, but it also adds the auth-free fact, so little is wasted.

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?

With an output schema present, return values need not be described, and the description covers matching rules, failure mode, auth, and inputs. It does not explain why latitude/longitude are needed (location-dependent menu/availability), a minor gap for a 'location-aware' tool.

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%, so the baseline is 3, but the description adds real meaning: itemId is resolved as a name (case-insensitive) rather than a stable ID, and it confirms the required combination of storeId/itemId/latitude/longitude. That goes beyond the schema's terse field descriptions.

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 names a specific verb (retrieve details) and resource (DoorDash menu item) and adds the distinguishing scope 'location-aware'. It never names a sibling such as doordash_store_menu or doordash_search_items, so the agent must infer the boundary, but the resource is 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?

It implies usage by stating the four required inputs and that no account/token is needed, which tells the agent this is an anonymous lookup. It gives no explicit when-to-use-vs-alternative guidance (e.g., versus doordash_store_menu for listing the whole menu), so usage is only implied.

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