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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for going further: it discloses that each result explains its catalog matches and that ranking follows relevance then title rather than popularity or editorial rating. Those ranking/explanation semantics are exactly the kind of behavior an agent cannot get from annotations.

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 short sentences, front-loaded with the core action, and mostly dense. 'Each result explains its catalog matches' is a little vague and leans on an unexplained notion of 'catalog matches', slightly diluting an otherwise tight description.

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 6-parameter, no-output-schema read tool, this covers the matching model, ranking model, and result explanation. It is largely sufficient, though it says nothing about limit/exclude behavior or what happens when no games match, leaving a small completeness 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 coverage is only 50% (tags, exclude, limit are bare), and the description compensates by explaining the matching mode that separates parameters: 'Matches catalog text and optional exact category/tags.' That tells the agent preferences is fuzzy text matching while category/tags are exact, which the schema alone does not convey for tags.

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 verb and resource ('Find browser games') plus the discriminating scope ('matching stated gameplay preferences and device'). It also clarifies what makes this a recommender rather than a plain search ('ordering is relevance then title, not popularity or an editorial rating'), which implicitly distinguishes it from search_games — but it never names the sibling 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?

Usage is implied by 'matching stated gameplay preferences' — the agent can infer you call this when you have a preference phrase. However, no alternative tool is named and there is no explicit when-not-to-use guidance, despite search_games being an obvious adjacent sibling.

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