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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-call behavior are covered. The description adds a genuinely useful behavioral fact not in the annotations: no DoorDash account or token is required. It does not describe rate limits, freshness, or scheduling semantics beyond the noun 'schedules'.

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 tight sentences with the capability front-loaded and the prerequisite/auth note second. No filler; each clause carries information, though the parameter restatement is slightly redundant with the schema.

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 explanation, and the description covers inputs and auth adequately. However, for a tool sitting in a dense doordash_store_* family, the absence of any routing guidance against siblings leaves a real gap.

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 all three parameters are already documented in the schema. The description merely restates the required parameter names without adding format, unit, or coordinate-system guidance beyond what the schema provides, 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 resource ('DoorDash store fulfillment details, delivery options, and schedules') and a location-aware scope, which is clearly distinct from menu/review siblings like doordash_store_menu or doordash_store_reviews. It stops short of explicitly naming the sibling it differs from (e.g. doordash_store_info), so an agent must infer the split.

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 states the required inputs and notes that no account/token is needed, but gives no when-to-use guidance and no differentiation from the many other doordash_store_* siblings. An agent has no explicit signal for choosing this over doordash_store_info.

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