doordash_search_autocomplete

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It explicitly states that no DoorDash account or caller-supplied token is required and that it uses the Android mobile guest search experience, adding valuable context beyond the name. However, it does not describe the response format or potential rate limits, though these are less critical for a simple read operation.

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?

The description is two concise sentences that are front-loaded with the primary action. Each sentence contributes meaningful detail: the first defines the tool's purpose, and the second adds context about the return type and authentication-free nature. No redundant or wasted words.

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?

Given the simple 3-parameter schema and no output schema, the description provides the essential purpose and context, including the no-auth requirement. It lacks an explicit description of the return value structure, but for an autocomplete tool, the level of detail is sufficient for an agent to invoke it correctly.

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 baseline is 3. The description adds only minimal context beyond the schema, such as 'near a location' linking to latitude/longitude. It does not provide additional syntax or format details for the parameters.

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 clearly states the tool's function with a specific verb and resource: 'Get DoorDash pickup search suggestions.' It further specifies it returns pickup restaurant matches from the Android mobile guest search experience, distinguishing it from sibling tools like doordash_search or doordash_explore by focusing on autocomplete suggestions for pickup.

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 implies usage for generating search suggestions but does not explicitly state when to use this tool over alternatives such as doordash_search or doordash_feed. No exclusions or alternative tools are mentioned, leaving usage guidance solely implied by the action described.

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