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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context that annotations cannot: it enumerates the returned fields (award, credited AI tools, engine, pageUrl, playUrl), which is valuable given there is no output schema. It omits pagination and rate-limit behavior, keeping it short of a 5.

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?

Three tight sentences: purpose first, filter usage second, return shape third. Every sentence earns its place with no redundancy or filler, and the most important scoping information is front-loaded.

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 two-parameter, read-only list tool with full schema coverage and annotations covering the safety profile, the description closes the remaining gap by explaining the return fields in the absence of an output schema. An agent has everything needed to call and interpret it 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 coverage is 100%, so both parameters (jam, limit) are already fully documented, establishing a baseline of 3. The description supplies example jam-name formats, but the schema itself already states that "vibe-jam-2026" and "Vibe Jam 2026" both work, making the added value marginal rather than additive.

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?

Starts with a specific verb (List) and a precisely scoped resource (AI-made jam winners and category awardees), naming concrete sources like Vibe Jam and the AI Browser Game Jam. This resource is plainly distinct from siblings such as list_trending, search_games, and random_game, so an agent can route to it without ambiguity.

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 explains how to use the jam filter ("Filter with a jam name such as..."), which implies the intended invocation context. However, it never says when to prefer this tool over search_games or list_trending, nor states any exclusions or when-not-to-use conditions, leaving the routing decision to inference.

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