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

Annotations already establish the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description's job is to add context — and it does: sellers are anonymized into letters, letters reflect arrival order rather than rank, and they match the event page. It also discloses the 10-live-listing threshold and the 720-hour cap, though it says nothing about empty results or error behavior.

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 resource, then walks the three views in a compact parallel structure with the default flagged inline. It is dense and slightly run-on, but nearly every clause carries information an agent needs.

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?

With no output schema, the description must carry the return-value burden, and it names the concrete metrics per view (active sellers, top shares, hhi, coverage; hour-by-hour movement; prices and listings per section). Coverage is good for a three-mode tool, though output shape and pagination remain only lightly sketched.

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 genuine semantics beyond the schema: letters are an arrival order not a rank and align with the event page, and the market view's 10-listing eligibility rule explains when the 'sellers' parameter can be populated at all.

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 the resource precisely ('One event's sellers, anonymously and by letter') and enumerates three concrete views (now/series/market) with what each returns. It also names the three sibling tools it supersedes, so an agent can distinguish it from get_event_seller_concentration, get_event_seller_series, and get_event_seller_market without opening 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?

Gives per-view selection criteria: 'view now (the default)' for concentration, 'view series' for hour-by-hour movement, 'view market' for chosen sellers' prices and listings. It also states the gating condition for the market view ('only a seller that reached 10 live listings can be chosen') and explicitly declares it replaces three named siblings.

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