fetch_reviews

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

No annotations provided, so description carries full burden. It mentions returns review text, author info, timestamps, voting data, and supports time-bounded queries and review bomb filtering. However, it does not disclose side effects, auth requirements, rate limits, or data freshness. Minimal transparency beyond parameter descriptions.

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 sentences covering main action and key features. No wasted words. Could be improved by front-loading essential info more clearly, but sufficiently concise for a tool with many parameters.

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?

Description provides a high-level overview of what the tool does and its capabilities. However, it lacks details about output format, pagination mechanics, or error handling. Given the complexity (10 params, no output schema), more context would help an agent use it effectively.

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 baseline is 3. Description adds high-level context ('advanced filtering and pagination support') but does not provide significant additional meaning beyond the detailed schema descriptions for each parameter.

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?

Description clearly states 'Fetch actual user reviews for a Steam game' with specific verb and resource. It distinguishes from sibling tools like analyze_reviews and get_game_info by mentioning advanced filtering and pagination.

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?

Description implies usage for fetching reviews with filters, but does not explicitly state when to use this tool vs siblings like analyze_reviews or search_steam_games. No when-not-to-use or alternative guidance provided.

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