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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), and the description adds real value beyond them: it discloses that pricing is live from a connected order book and that the return includes an upcoming-events feed designed to tee up get_ticket_listings. It stops short of describing pagination, freshness windows, or coverage limits on the calendar.

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?

Front-loaded with the core purpose before the usage examples, and every sentence earns its place by adding routing or payload information. Slightly long because of the repeated example phrasings, but not wasteful.

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 a full output schema present, the description needn't explain return values, yet it still summarizes the composite payload and the downstream call it enables. For a single-parameter read tool with rich annotations, nothing an agent needs to invoke it correctly is missing.

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?

Only one parameter and schema coverage is 100%, so the schema already documents venue_id and its origin in search_venues. The description adds no format, range, or sourcing detail beyond what the schema provides; baseline 3 is appropriate.

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+resource (pull full venue info) and enumerates the composite payload: XP venue data, upcoming-events calendar, and live resale/primary pricing. It explicitly contrasts itself with get_ticket_listings, so an agent can distinguish it from siblings without opening schemas.

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?

Gives explicit when-to-use (after search_venues, or when the user asks about upcoming shows) with concrete example phrasings, plus an explicit when-not-to-use routing to get_ticket_listings for seat-level data. Nothing is left to inference.

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