review_top_apps

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuine workflow context by positioning the call as the competitor-discovery step preceding review_fetch, though it says nothing about rate limits or result volume beyond the schema's limit.

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 short sentences, the capability statement front-loaded and the usage hint second, with no filler. Every clause earns its place.

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 an output schema present and rich annotations, the description need not explain returns, and the schema documents the six optional params. Nothing an agent needs to invoke the tool correctly is missing, though it could clarify category/country applicability more directly.

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 83%, well above the threshold where the schema carries the load. The description restates the chart and store options but adds no syntax or defaulting guidance beyond what the schema already documents, so baseline 3 applies.

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 (list) and resource (current top charts) and enumerates the chart variants for both App Store and Steam, so an agent immediately knows what comes back. It is clearly distinct from review_search_apps/review_fetch by being a chart-listing rather than a lookup, but it does not name those siblings explicitly.

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?

Directs the agent to use it to pick competitors before fetching reviews, giving a concrete discovery-then-detail workflow. It lacks an explicit 'when not to use / use X instead' clause, so the routing is implied rather than stated.

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