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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, assuring safe, read-only behavior. The description adds value by detailing the returned data (reviews, state per store) and automatic collection process, without contradicting annotations.

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, concise and front-loaded with the core purpose. Every sentence is informative without redundancy, making it efficient for an AI agent to parse.

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?

Given the presence of annotations and an output schema, the description provides sufficient context: it explains the data sources, what is returned, and the automatic collection. It could be slightly more explicit about the 'monitoring state' aspect, but overall it is complete for a read-only tool with structured output.

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 the baseline is 3. The description does not add extra meaning beyond what the schema provides for 'page' (default 1, 20 per page) and 'startup_slug' (from list_my_startups). No additional parameter context is given.

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 retrieves public reviews from Google Play and App Store, specifying the data included (rating, text, developer response) and that it's automatically collected via app links. It is distinct from sibling tools like 'get_releases' or 'get_waitlist' which serve different purposes.

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 implies usage for monitoring reviews but does not explicitly state when to use this tool vs alternatives, nor when not to use it. It provides context for review retrieval but lacks clear guidelines on exclusions or prerequisites beyond the required 'startup_slug' parameter.

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