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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-data reach are covered. The description adds that results are geo-personalized and match the homepage feed, which is meaningful context, but it says nothing about result count, freshness, or pagination.

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?

A single front-loaded sentence that identifies the source, the personalization mechanism, and the parity with the homepage. Nothing extraneous.

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?

An output schema exists, so return values need not be described, and annotations carry the read-only profile. For a two-parameter feed lookup the definition is essentially sufficient, with only the sibling-routing guidance left implicit.

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 100% with only lat/lon, so the schema already documents both parameters. The phrase "for a coordinate" confirms they are a pair rather than adding format or range detail 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?

States a specific resource ("trending near you" event feed) and its mechanism (geo-personalized, driven by a coordinate), plus the useful framing that it mirrors SeatGeek's homepage rather than a query-driven result set. It implicitly separates itself from seatgeek_events_near/search, but never names those siblings outright.

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 description implies when this applies (you have a coordinate and want the editorial trending list), and "the same list its homepage renders" hints that it is not query- or filter-driven. However, it gives no explicit when-to-use versus seatgeek_events_near, seatgeek_search, or seatgeek_cities, so the agent must infer the routing.

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