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

With annotations already declaring readOnlyHint=true and openWorldHint=true, the description still adds genuinely useful auth context: 'no DoorDash account or token is required.' Combined with the note that output is grouped into sections, this goes beyond what the annotations convey.

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, no wasted words, with the core purpose front-loaded ahead of the requirements. Efficient and easy to scan, though it could carry slightly more routing value.

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 tool is a simple read with a full output schema, so return values need no explanation. Purpose, required inputs, and auth expectations are covered; the only gap is guidance on choosing this tool over sibling menu/store endpoints.

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 schema already documents storeId, latitude, and longitude. The description only restates that these three are required, adding no format or semantic detail beyond the structured fields, so the baseline 3 applies.

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 and resource ('DoorDash mobile menu grouped into sections') and implies the store-scoped retrieval. It clearly describes what the tool returns, but does not explicitly distinguish itself from siblings like doordash_store, doordash_store_info, 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?

It states the required inputs (storeId, latitude, longitude) and that no account is needed, but gives no explicit when-to-use guidance or alternatives. An agent must infer when this menu tool is preferable to doordash_store or doordash_store_item.

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