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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds genuinely useful behavioral context: the service account requirement, 'most recent' ordering, truncated review text, and pagination via a returned page token. This goes beyond what the annotations alone provide.

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 compact and information-dense: the first sentence states purpose and output fields, the second covers the prerequisite, and the third explains pagination. There is no filler or unnecessary repetition.

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?

Combined with the complete parameter schema, output schema, and annotations, the description covers the essential context an agent needs: what the tool returns, which app scope it applies to, the service account requirement, and how to paginate. No critical decision or invocation information is missing.

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 all four parameters already have meaningful descriptions. The tool description does not add significant parameter-level semantics beyond the natural context of 'most recent reviews' and pagination, so the baseline of 3 is appropriate.

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 states exactly what the tool does: lists recent Google Play reviews for an Appskyline app, and enumerates the returned fields (star rating, truncated text, app version, device, language, reply status). This clearly distinguishes it from sibling tools such as list_apps and list_keywords.

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 clear usage context: it is for fetching reviews for a specific app, requires a configured Google Play service account, and uses pagination. It does not explicitly compare against alternatives, but the sibling tools are clearly about different resources, so the invocation situation is readily inferable.

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