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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive). The description goes further by disclosing the result envelope (data in tasks[0].result, outcome in tasks[0].status_code) and the non-obvious HTTP-200-on-rejection quirk, which is genuinely useful error-handling context beyond annotations. It stops short of pagination or result-count behavior.

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?

Front-loaded with the resource and scope, then pricing, then the envelope contract, then the alternative tool. Every sentence carries distinct information; the injected pricing block is boilerplate rather than author bloat.

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 single-ID fetch with an output schema, an agent has everything it needs: how to obtain the ID, that the call is free, how to read the response envelope, how to detect a rejected request, and where to go for adjacent data.

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 100% and the single parameter's meaning ('DataForSEO task ID') is already documented. The description adds provenance for that ID (it comes from the submit call), which is mildly useful but not more than what the schema and sibling references imply. Baseline 3 applies when the schema carries the load.

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 ('Buyer reviews for one Google Shopping product') and enumerates the returned fields (rating, text, author, date). It distinguishes itself from siblings by naming the queueing tool it depends on and routing product-spec lookups to get_dataforseo_merchant_google_product_info_fetch.

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 the precondition explicitly ('from a task queued by post_dataforseo_merchant_google_reviews_submit') and names the alternative tool plus the condition that selects it (product specification and sellers). An agent knows when to call this and when to route elsewhere.

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