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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful non-annotation context: the billing/quota model ('every 25 reviews returned count as one result, rounded up per request'). It stops short of noting rate limits or how partial failures across multiple apps/countries are reported.

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 sentences, zero padding. The capability statement comes first and the quota caveat follows, so the reader gets the essential semantics before the cost model.

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 no output schema, the description carries the return-shape burden, and the '25 reviews = one result' rule goes a long way toward setting expectations. Given 8 parameters and multi-app/multi-country scope, it is nearly complete; a note on ordering defaults or cross-app result grouping would close the gap.

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 63%, so the schema documents most parameters (apps, since, keywords, countries, maxReviewsPerApp). The description largely restates those same filters and adds no format or default detail the schema lacks, 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+resource ('Get Apple App Store reviews for apps') and immediately scopes the accepted identifiers (name, numeric ID, URL), countries, and filter axes. An agent knows exactly what this tool retrieves and at what granularity.

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?

Usage is implied by the filter list (rating, keywords, date, countries), but there is no explicit when-to-use or when-not guidance, and the siblings (ats_jobs, domain_whois, youtube_transcript, etc.) are unrelated enough that no routing note is strictly required. Minimum viable.

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