doordash_auth_check

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

With no annotations, description carries full burden. It discloses the behavior: checking login status and returning instructions if not authenticated. Could be more specific about what 'instructions' entails, but sufficient for a simple auth check.

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?

Two sentences: first states purpose, second gives usage guideline. Extremely concise with no unnecessary words. Every sentence adds value.

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 auth check with no parameters and no output schema, the description covers purpose and usage context adequately. It mentions return value (login status and instructions) and prerequisite nature. Could be more detailed about the instructions, but overall complete enough.

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?

No parameters (0), so baseline is 4. Description adds no parameter info because none exist; schema coverage is 100% (empty schema). No need for additional semantics.

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?

Description clearly states the tool checks login status and returns instructions if not authenticated. It distinguishes itself from siblings by being a prerequisite check, contrasted with operations like doordash_add_to_cart or doordash_checkout.

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?

Explicitly says 'Call this before any other DoorDash operations,' providing clear when-to-use guidance. It doesn't mention when not to use alternatives, but the context makes it obvious.

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