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

While annotations already mark the operation as read-only, idempotent, and non-destructive, the description adds valuable behavioral context: the DataForSEO envelope, where data lives, how status is communicated, and that rejected requests still return HTTP 200. This goes well beyond the 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?

Four short sentences with no wasted words. The key purpose is front-loaded, the response envelope is explained in the middle, and the alternative tool is given last. Every sentence earns its place.

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 one-parameter fetch tool with an output schema and safety-relevant annotations, this description is complete. An agent knows what to pass, what it will get, how to interpret the response, and how this tool differs from related siblings.

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?

The single parameter is fully described in the schema as a DataForSEO task ID, giving the baseline of 3. The description enriches this by explaining that the ID comes from a task queued by the submit operation and maps to tasks[0].result, so the agent understands what kind of ID to pass.

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 returns: buyer reviews (rating, text, author, date) for one Google Shopping product. It also distinguishes itself from the sibling for product specifications and sellers, so an agent can tell the tools apart without opening schemas.

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?

It explicitly names the prerequisite task created by post_dataforseo_merchant_google_reviews_submit and names the alternative sibling for product specifications and sellers. This gives clear when-to-use and when-not-to-use guidance.

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