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

Annotations declare this is a state-changing, non-idempotent operation. The description adds valuable behavioral detail beyond annotations: the 30-minute lifetime, the required agent_session_id propagation, and the customer-facing URL. It does not cover failure modes or expiry handling, keeping it from a 5.

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 tightly written sentences with no filler. The session lifetime and required session-id propagation are front-loaded before the secondary confirmation URL detail.

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 explains the two key return values (agent_session_id and confirmation URL). Annotations cover the safety profile. It stops short of describing expiry behavior or authentication prerequisites, but is otherwise complete for a session-starter 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 100% for the single restaurant_id parameter, so the schema already provides full parameter meaning. The description adds only the phrase 'against a specific restaurant,' which does not deepen understanding beyond the schema's canonical-id guidance.

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 and resource: opening a 30-minute transactional session against a restaurant. It distinguishes itself from siblings by naming the downstream order tools that depend on the returned agent_session_id.

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?

Clearly implies this must be called before place_order, cancel_order, request_bill, waiter_call, and apply_promo, and explains sharing the confirmation URL with the human. It lacks explicit when-not guidance or alternative session-starting tools, but the workflow context is strong.

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