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 genuinely useful behavioral context beyond that: no account or caller token is required, which tells the agent this is an unauthenticated read and removes a pre-flight auth step.

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?

A single tight semicolon-joined construction: purpose and scope first, then routing to siblings. No filler sentences, and the key information is 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?

An output schema exists, so return values need not be described, and the annotations carry the safety profile. Auth requirements and sibling routing are stated; only marginal additions (e.g. pagination or result limits on reviews) are missing for a three-required-param read 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 description coverage is 100%, so storeId, latitude and longitude are already documented at the property level. The description only echoes that the call is made at a latitude/longitude and adds no format, range or fallback detail beyond the schema — 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 (Fetch) plus resource (DoorDash store ratings and customer-review items) scoped to storeId/latitude/longitude. It also names the siblings it is not (doordash_store, doordash_store_info, doordash_store_item), so an agent can separate it from the other DoorDash tools without opening a schema.

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?

Routes the agent with explicit alternatives: doordash_store for store details, doordash_store_info for service details, doordash_store_item for one menu item. That implies when to pick this tool, but there is no explicit 'use this when you want reviews' statement or exclusion clause.

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