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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds a useful behavioral caveat by labeling availability as 'crawl-time,' implying the data is a snapshot that may lag real-time conditions, which an agent needs to know before relying on it. It stops short of describing any staleness window or exact provenance.

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 waste. The record contents are front-loaded and the usage condition follows, so the agent gets purpose before guidance.

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?

An output schema exists, so return values need no further explanation, and the description still summarizes the payload shape. For a single-record lookup with one required param and clear annotations, nothing an agent needs to call it correctly is missing.

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% for the single store_id parameter, and the schema already shows the format example ('454089'). The description only restates 'by store id,' adding no syntax or lookup guidance beyond the schema, 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?

States a specific verb and resource ('Returns one DoorDash store dataset record by store id') and enumerates the record's contents (identity, contact, address, coordinates, tags, crawl-time pickup availability). This clearly differentiates it from the sibling search/facets/nearby tools, so an agent can tell it fetches one record rather than a list.

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?

Explicitly states the when: 'Use this after search when you already have a store id and want the full record.' That gives a clear prerequisite (an existing store id) and a use context, though it references a generic 'search' rather than naming the specific sibling tool (datasets_doordash_stores_search).

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