doordash_feed

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

With no annotations provided, the description carries the full burden. It discloses that metric fields are omitted rather than estimated when the upstream feed doesn't report them, and explicitly states no authentication is required. It could add more about pagination or rate limits, but the key behavioral traits are covered.

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 three sentences, each earning its place: what it returns, how missing fields behave, and the auth requirement. It is front-loaded with the core purpose and avoids redundancy.

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 read-only feed tool with 100% schema coverage and no output schema, the description covers the essential behavior, return fields, and auth requirements. It could mention pagination behavior or rate limits, but nothing critical is missing for an agent to call 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 schema already documents all four parameters. The description adds context that latitude/longitude are consumer coordinates and that limit/offset control pagination, but it doesn't add much beyond what the schema provides. Baseline 3 is appropriate.

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 states a specific verb ('Get'), a specific resource ('DoorDash store discovery feed'), and the key scope ('nearby stores for a location from the Android mobile guest experience'). It also lists the returned fields, which clearly distinguishes it from sibling tools like doordash_search, doordash_explore, and doordash_store.

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 clearly indicates this is for the discovery feed surface and notes it requires only latitude/longitude, with no account or token. It does not explicitly name sibling alternatives or state when not to use it, but the context of 'discovery feed' and 'guest experience' provides clear usage context.

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