steam_reviews

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

No annotations provided, so the description must disclose behavior. It notes credential-free, cursor pagination, and aggregate behavior. Lacks details on error handling, rate limits, or invalid appid scenarios, which would enhance transparency.

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 sentences: first sentence states purpose, second explains pagination and aggregate, third notes credential-free. Front-loaded and no fluff. Could be slightly more concise but well-structured.

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?

With 8 parameters and no output schema, the description covers key aspects: pagination, aggregate, and credential-free access. It does not explain all parameters beyond schema, but that is acceptable given high schema coverage. Minimal but adequate.

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 baseline is 3. The description adds value by explaining the cursor parameter's role in pagination and when aggregate data populates, which is beyond the schema's basic descriptions.

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 lists reviews for a Steam app with pagination and aggregate data. The verb 'List' and resource 'reviews for a Steam app' are specific. However, it does not differentiate from similar sibling tools like datasets_steam_reviews_search, so not a 5.

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?

Provides explicit pagination instructions: aggregate only on first page, pass cursor back for subsequent pages. Also notes credential-free usage. But lacks when-to-use vs alternatives or when-not-to-use hints.

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