get_app_reviews

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

Without annotations, the description carries the burden of disclosing behavior. It reveals the output content (verdict, positive %, count), but does not state side effects (though a getter is likely read-only), default behavior for the 'filter' parameter, or any rate limits/errors. This is partially transparent but lacks depth.

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 two sentences, front-loaded with the core purpose, and the second sentence adds a practical usage tip. Every word earns its place with no redundancy or 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?

The tool has no output schema, no annotations, and a zero-coverage input schema. The description provides the primary output metrics but fails to explain the filter parameter, default settings, or how results vary by filter value. This leaves the tool incomplete for an agent to predict behavior across all parameter combinations.

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 0%, so the description must compensate. It does not explain the 'filter' parameter or its enum values, leaving ambiguity about what 'positive' or 'recent' mean in context. The parameter names are self-explanatory to some degree, but the description adds no value beyond 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 clearly states the tool's purpose: 'Steam user review sentiment for a game' and lists the specific metrics returned (overall verdict, positive %, total review count). It distinguishes itself from siblings by focusing on reviews, though it lacks an explicit verb like 'Get' or 'Retrieve'.

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 gives a usage context: 'Use alongside opencritic-mcp critic scores for a complete quality picture,' suggesting when the tool is useful. However, it does not mention alternatives or when not to use this tool, leaving the guidance implied rather than explicit.

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