doordash_search

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states that the search operates on the 'Android mobile guest catalog' (indicating a public, guest-facing data source) and that no account or token is required, which is valuable for the agent. It does not mention rate limits or pagination, but for a search tool this is adequate.

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 concise and front-loaded: the first sentence states the core purpose, followed by additional context about the catalog and auth requirements. Every sentence earns its place with no redundancy or filler.

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 tool's complexity (8 parameters) and the absence of an output schema, the description covers the essential context: what is searched, where it searches, and the authentication requirement. It does not describe return values, but for a search tool this is usually implicit. The description is sufficiently complete for effective use.

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 no specific parameter semantics beyond what the schema already provides, apart from the general note that 'optional result filters' are supported, which is already evident from the schema's parameter descriptions.

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: 'Search DoorDash pickup restaurants.' It specifies the resource (DoorDash pickup restaurants), the action (search), and additional context about the Android mobile guest catalog. However, it does not explicitly distinguish itself from sibling tools like doordash_explore or doordash_feed, which may offer overlapping search functionality.

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 provides clear context for when to use the tool: when searching for pickup restaurants near a location, especially without authentication ('No DoorDash account or caller-supplied token is required'). It does not mention exclusions or alternative tools, but the phrasing implies this is the go-to for unauthenticated pickup restaurant searches.

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