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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds some genuine behavior context: results are emulated to match live search, personalized factors are ignored, and check_url can be used in Incognito to validate relevance. It omits other behavioral facts such as the 30-day retrieval window (which lives only in the schema) and pagination/result-size 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?

The body is padded with marketing prose about emulation accuracy and personalization that does not help an agent invoke the tool, plus a boilerplate pricing block. The front-loaded sentence points at the wrong operation (returning profiles rather than fetching a task's results), so the structure buries the one fact an agent needs.

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?

An output schema exists, so return values need not be explained. However, for an async task-fetch endpoint the description should make the submit-then-fetch flow and the required task id explicit, and it does not; combined with no usage guidance, an agent cannot confidently sequence this tool against its submit sibling.

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% with a single well-documented 'id' parameter, so the baseline is 3. The description adds nothing about the id beyond what the schema already says (UUID task identifier, usable for 30 days).

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 the resource ('a list of business profiles listed on the Trustpilot platform') and implies a search-derived result set, but it reads like the *submit* endpoint's copy rather than a fetch-by-task-id operation. It never says the tool retrieves results of a previously created task using an id, so the specific verb+operation is muddled and the submit sibling is not referenced.

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?

There is no when-to-use guidance, no mention of the prerequisite submit step (post_dataforseo_business_trustpilot_search_submit) that produces the required id, and no routing versus the sibling fetch tools for other sources (Tripadvisor, Google reviews). The only hint of usage context is the check_url verification remark, which is incidental.

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