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

Goes well beyond the annotations (readOnly/idempotent/openWorld) by disclosing real-time execution, a cost of 1 API credit, and the exact return shape: the complete TicketsData API response unchanged, always as a JSON-file link and inline when small. It also flags unsupported marketplaces, which is behavioral context the annotations cannot convey.

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-loads the purpose and workflow before cost, return format, and parameter routing, and every sentence carries actionable information. It is somewhat dense with five sentences of guidance, but none is filler, so it stays close to optimal.

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?

Without an output schema, the description compensates by explaining that the raw API response is returned as a JSON link plus optional inline. Combined with cost, real-time behavior, platform coverage, and parameter routing, an agent has everything needed to call it correctly.

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 the baseline is 3, but the description adds real routing value beyond the schema: it resolves when to use performer_url versus venue_url (dice only) and clarifies that eventbrite organizers go in performer_url. This meaningfully reduces parameter-selection error even though the per-parameter text is already present.

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 ('List upcoming events') and scopes it to a performer/venue page on one marketplace. It also distinguishes itself from siblings by naming get_event_listings and compare_marketplaces as downstream tools for the URLs it produces.

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 states when to use it ('Use it to discover event URLs, then pass one to get_event_listings or compare_marketplaces') and names the alternative tools. It further gives per-platform routing rules (performer_url for most, venue_url for dice only, eventbrite organizer URL) and excludes unsupported platforms (viagogo, axs).

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