ticketweb_venue

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

With no annotations, the description carries the behavioral disclosure burden. It states the exact return composition (name, address, one page of upcoming events) and explicitly normalizes an empty events list as a valid 'no upcoming events' response. It does not cover error behavior or default pagination, but for a simple read tool the edge-case disclosure adds real value.

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?

Three short sentences with the core purpose front-loaded. The first two sentences are slightly redundant ('Get a TicketWeb venue' vs 'Returns one TicketWeb venue's detail'), but the rest is free of filler and the edge-case caveat is useful.

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?

For a simple two-parameter read tool with no output schema, the description covers the input via schema and the output via a clear summary plus the key empty-response edge case. It does not show the exact response structure or error cases, but it gives an agent enough to invoke and interpret the result.

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?

The input schema already documents both parameters completely, including the numeric id and the one-based page range 1-50. The description's mention of 'page 1' and 'one page' only restates what the schema implies, adding no format or constraint information beyond the schema.

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 opens with a specific verb and resource ('Get a TicketWeb venue') and clearly states the return payload: venue detail (name, address) plus one page of upcoming events. This differentiates it from ticketweb_search and ticketweb_event without needing to open any schema.

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 tool's use is implied: retrieve a known TicketWeb venue by id and read its upcoming events. However, it never explicitly mentions when to prefer this over ticketweb_search or ticketweb_event, and no alternative names or exclusion conditions are given.

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