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

Annotations already cover readOnly/openWorld/non-destructive, and the description adds substantial context beyond them: the return type is an image, charts are not universal, the missing-chart fallback is spelled out, and no sign-in is required. It stops short of describing image format or any size/pagination characteristics, but the operational behavior is well covered.

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 trigger phrases, then the layout-vs-photo clarification, then failure handling and auth. Every sentence carries information, though the anti-photo warning is emphasized twice ('must never be described as one'), which is slightly redundant.

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?

Simple one-parameter read tool with an output schema, and the description still covers the return artifact, the not-every-venue failure mode, the fallback tool, and the auth requirement. Nothing an agent needs to select or 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 description coverage is 100%, so the schema fully documents event_id and its provenance (search_market, search_events, get_event_details). The description adds no additional parameter meaning, which is the expected baseline here.

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 ('Returns the venue seating chart as an image') and explicitly defines scope as the venue LAYOUT. It distinguishes this from the view-from-seat photo it must not be confused with, and from get_ticket_listings which supplies section/row text.

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?

Opens with concrete user utterances that trigger it ('where is 104', 'show me the map', 'is that behind the stage') and points to get_ticket_listings as the alternative when a chart is missing. Both the when-to-use and the when-not condition are explicit.

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