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

Annotations cover the safety profile, but the description adds substantial context they do not: duplicates are skipped, each call runs ~40 seconds and returns progress plus a job_id, free workspaces are capped at 25 reviews/month, the apify_token is never stored and is billed to the user's own Apify account, and it must be re-passed on every job_id call.

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?

It is front-loaded with the core action and every clause carries information (supported sites, rate limits, continuation, fallbacks). It is a dense run-on paragraph with heavy parentheticals rather than scannable structure, which slightly hurts readability.

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?

For a 13-parameter mutation tool with no output schema, the description covers the essential operational facts: the paginated job_id loop, the preview step, allowance limits, and the fallback route. Minor gaps remain (error behavior beyond 'use_another_route', space_id resolution).

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 69%, so most params are documented structurally, but the description adds real semantics the schema lacks: the job_id/stop continuation protocol, why apify_token is unnecessary for certain sites, and the preview-first workflow. It does not explain status, low_rating_status, countries, or method beyond the enum values.

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 and resource ('fetches EVERY review ... from a public review page and imports them into a space') with scope qualifiers (all pages, photos, duplicates skipped). An agent can immediately distinguish this URL-scraping importer from the sibling import_testimonials.

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?

Gives explicit conditions: use preview=true first, and for Tripadvisor/Product Hunt/Clutch (or exhausted allowance) the server returns 'use_another_route' with the alternatives (Claude's own fetch or an apify_token). It also explains the multi-call continuation via job_id. It stops short of contrasting with the sibling import_testimonials tool, so it is not a full 5.

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