get_consumer_account_status

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

Annotations already declare read-only, idempotent and open-world behavior, so safety is covered. The description adds genuinely useful operational context the annotations cannot convey: it needs a saved session and a manually launched CDP Chrome instance, which tells the agent the call will fail without local browser setup. It does not say what a failed verification returns.

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 short sentences, zero filler. The action is front-loaded and the prerequisite constraint follows immediately, which is the right ordering for an agent scanning for blockers.

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 parameterless, read-only verification call with full annotation coverage, the description covers action and prerequisites. With no output schema, it could have said what success/failure yields (boolean vs. account payload), which is the only remaining gap.

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?

The tool takes zero parameters, so the schema baseline of 4 applies; there is no parameter semantics for the description to add or omit.

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?

States a specific verb ('Verify') and a clear resource ('the connected local DoorDash account'), which cleanly separates it from the order-oriented siblings such as get_consumer_order_status. It does not explicitly name alternatives, so it stops short of a 5, but the resource/scope is unambiguous.

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?

Usage is only implied: the tool checks whether the locally connected account is authenticated, and the second sentence states the prerequisites. There is no explicit when-to-use/when-not guidance or routing to a sibling, so this is adequate but not directive.

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