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

Annotations already mark this as readOnly and non-destructive, so the description adds context beyond them: it is public, cross-event, ranked for display, and optionally filterable by event. No contradictions with annotations exist, and the read-only nature is reinforced by calling it a gallery.

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?

The description is compact, front-loads the core purpose, enumerates key fields, and ends with a routing hint to a sibling. Every sentence earns its place with no filler.

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 read-only browse tool, the description covers the resource scope, returned fields, optional filtering, and the key sibling distinction. Pagination details are available in the schema. It lacks an explicit statement about the list envelope or ordering criteria beyond 'ranked for display,' but this is a minor gap.

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%, so the schema already documents page, page_size, and event_slug. The description adds minimal extra meaning, only restating 'optionally narrow to one event' for event_slug. This meets the baseline but does not significantly enhance 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 uses a specific verb ('Browse') and names the exact resource ('public, cross-event showcase'), then enumerates what is shown (title, tagline, team name, vote count, cover image). It explicitly contrasts itself with event_leaderboard, making sibling differentiation clear.

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?

It states the intended use case ('public gallery') and provides a concrete alternative: use event_leaderboard when judged rankings for one event are needed. This gives an agent clear routing guidance without ambiguity.

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