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

Annotations already declare the full safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description adds genuinely new context: this renders a visual picker, embeds a request-and-pay form, and is host-dependent. The only wrinkle is that 'pay the platform service fee' sits inside a readOnly tool, which could momentarily mislead, though the mutation is actually delegated to sibling tools like request_table/create_checkout.

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 tight sentences with the primary action front-loaded and zero filler; the host qualifier and the data-source comparison each earn their place. It stops just short of a 5 because the payment clause adds a slight ambiguity without clarifying the actual flow.

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?

An output schema exists, so return values need not be described, and the description adequately conveys that this is a visual rendering of availability data plus a request/pay form. It is nearly complete for a UI-render tool, with only minor gaps around host-capability fallback and how the embedded form maps to sibling tools.

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 only 40% (5 params, 2 required), so the description is expected to compensate but largely does not. It references 'venue' and 'night' (the date), yet adds no format, default, or meaning for zone, party, or max_min_spend, and provides no syntax detail beyond the schema's own 'YYYY-MM-DD' and venue-id notes.

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 names a specific verb and resource ('Render the interactive table picker') and pins the scope to 'a venue and night.' It also distinguishes itself from the availability list by noting it shows 'Same table data as the availability list,' implicitly separating it from check_availability, though it never names that sibling explicitly.

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 parenthetical '(ChatGPT / MCP Apps hosts)' gives a real host-capability constraint for when this tool is usable. However, it never states when to prefer this over check_availability (the list form of the same data) or what happens if the host lacks interactive UI support, leaving the main routing decision to inference.

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