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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: coverage is limited to UPFRONT-chart venues, missing row data between front and back is interpolated and flagged 'estimated', and viewPicture is a 3D render rather than a photo.

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 capability and example questions, then parameter definitions, then caveats. Every block earns its place, though the trailing paragraph explaining viewPicture/sectionPage/source adds length that could be tightened slightly.

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?

No output schema exists, and the description compensates by naming the return fields (viewPicture, sectionPage, source) and explaining what viewPicture actually is. Coverage limits and the estimated-value flag round out what an agent needs to call and interpret this 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 description coverage is 0%, so the description must carry the load and it does: venue accepts names and abbreviations ('MSG'), section accepts number or ticket-style name ('Field Box 22'), and row is optional with a documented estimation behavior for interior rows.

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 combination ('What one section of a venue is like') and enumerates the exact facts returned: location, distance from the field/court/stage, height, covered rows, and a view picture. The example questions ('is section 314 at Lumen Field covered?') make the boundary against venue_info and get_seating_map obvious.

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?

Provides concrete triggering questions and two explicit scope exclusions: it has no row or seat counts, and it only covers venues with an UPFRONT seating chart (others return a message listing covered venues). It stops short of naming a sibling to use instead when the venue isn't covered or when row/seat counts are needed, so it isn't a full when/when-not/alternatives statement.

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