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

Adds real behavior beyond the annotations: a 30-minute lifetime, the session-id contract, and a customer-facing confirmation URL for human review. Annotations only declare readOnly=false/idempotent=false, so the expiry and chaining details are genuinely new. It stops short of saying what happens when the session lapses or whether a second call yields a fresh window.

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, zero filler, with the expiry/identity of the operation front-loaded and the required downstream usage spelled out second. Every clause carries actionable information.

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?

With no output schema, the description correctly carries the return-value burden by describing both the session id and the confirmation URL, plus the human handoff step. Only the failure/expiry path is unaddressed, which is a minor gap for a one-parameter 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?

The single parameter is fully documented in the schema ('Canonical restaurant id from get_restaurant or search_products'), so the baseline is 3. The description only restates it as 'a specific restaurant' without adding sourcing or format guidance beyond the schema.

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 action and object ('Open a 30-minute transactional window ... against a specific restaurant') and pins down the semantics with the expiry and scope. An agent can distinguish this from create_cart or get_cart without opening another schema.

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 names the downstream tools that require the returned agent_session_id (place_order, cancel_order, request_bill, waiter_call, apply_promo), making the prerequisite relationship clear. It does not contrast with create_cart/get_cart, so the 'when not to use' side is left implicit.

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