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

Annotations already cover readOnlyHint and openWorldHint, so the bar is lower, and the description adds genuinely new context: it is location-aware and requires no DoorDash account or token. It does not mention rate limits, caching, or error behavior, but the auth disclosure is real added value.

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: purpose first, prerequisites and auth second. No filler, and the key constraints are front-loaded.

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 three-parameter read-only lookup with full schema coverage, annotations, and an output schema, the description covers inputs and auth adequately. The one meaningful gap is failing to differentiate from doordash_store_info among the crowded doordash sibling set.

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% and every parameter already carries a description, so the schema does the heavy lifting. The description only restates that storeId, latitude, and longitude are required without adding format, range, or usage nuance 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 names the resource (DoorDash store metadata) and its scope (location-aware, mobile store), so an agent knows roughly what it retrieves. However, it never distinguishes this from the near-identical sibling doordash_store_info, leaving the agent to guess which to call.

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 and that no account/token is needed, which implies when the tool is usable, but there is no explicit when-to-use vs alternatives guidance and no mention of the sibling store tools. 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.