track_delivery

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-access profile is covered. The description adds valuable behavioral context by disclosing the returned live status fields and the stage progression (created → picked_up → delivered), which is especially useful because no output schema is present.

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 a single, well-structured sentence that front-loads the core value ('Live status straight from DoorDash') and then lists the returned fields. Every element earns its place with no 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?

For a simple one-parameter read tool with no output schema, the description adequately covers the return content. However, it omits any explanation of the required external_delivery_id and gives no usage guidance relative to siblings, leaving notable gaps for an agent invoking the 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 0%, so the description would need to explain the required external_delivery_id parameter. It does not mention the parameter at all, its expected format, or where to obtain it. The parameter name is somewhat self-explanatory, but no additional semantics are provided.

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 retrieves live delivery status from DoorDash, listing the specific returned fields: stage, Dasher name/location, ETA, and tracking URL. It distinguishes itself from sibling tools by being a tracking/status read rather than a quote, dispatch, update, or cancellation operation, though it does not explicitly name a sibling alternative.

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 phrase 'Live status' implies checking current delivery progress, but there is no explicit guidance on when to use this tool versus list_deliveries, get_delivery_quote, or update_delivery. No conditions, prerequisites, or exclusions are provided.

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