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

With no annotations provided, the description fully discloses that the hold is temporary, nothing is paid, the hold expires, and the tickets are not reserved until checkout is completed. This provides clear behavioral expectations.

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, no wasted words. The first sentence states the primary action, and the second sentence contains all critical caveats in a clear, highlighted manner (using caps).

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?

Despite no output schema, the description explains it returns a checkout URL. It covers prerequisites, constraints, and exclusions. The tool is straightforward and the description addresses all necessary context.

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 coverage is 100%, so baseline is 3. The description adds value by specifying the maximum quantities (10 tickets and 10 ticket types), which is not in the schema. It also references related tools (get_event_tickets, list_events) for obtaining parameter values.

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 clearly states the tool holds tickets for an event sold through Wix Events and returns a checkout URL. It uses a specific verb ('Hold tickets') and resource ('event sold through this site'), distinguishing it from sibling tools like create_booking or request_reservation.

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 provides when-to-use (event sold through this site) and when-not-to-use (events sold elsewhere like Sympla, Ingresse, Sesc), and names the alternative (use the event's own ticketUrl). Also states constraints (max 10 tickets and ticket types).

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