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

Annotations already declare readOnly, idempotent, non-destructive, and non-openWorld, so the safety profile is covered. The description adds useful scope ('actual published', 'public inspection only'), but does not disclose pagination behavior or that the catalog mutates across calls – that warning lives only in the offset schema field.

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?

Two tight sentences with the purpose front-loaded and no filler. The trailing 'choose a game yourself' is slightly clipped but overall efficient.

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 five-parameter tool with 40% schema coverage and no output schema, the description is on the thin side – it doesn't convey what the returned entries look like or how 'trusted evidence' ordering is determined. Rich annotations carry the safety side, but the return-shape gap remains.

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 40%, so the description must compensate. It does map filter-by-text (q), genre, and sort, covering three of five parameters, but adds no meaning for the enum values or the interaction between limit and the canonical catalog window. Baseline 3 fits.

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 states a clear verb and resource ('Read the actual published game catalog') plus the filter/sort dimensions. However, it never differentiates itself from the sibling tool 'store', which an agent could easily confuse with browse_store.

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?

'Public inspection only; choose a game yourself' implies a browse-for-yourself use case but names no alternative and gives no explicit when-to-use vs store, game_details, or public_replays. Usage is only weakly implied.

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