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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond them: results are emulated to match the search at task-setting time, personalized search factors are ignored, and results can be independently verified via check_url.

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 core purpose, but the body is verbose, repetitive, and marred by a missing sentence break ('Trustpilot platform The returned results'). The personalization note earns its place; the emulation-accuracy sentence is largely filler.

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 a single-param retrieval tool in a submit/fetch pair, the description omits the crucial fact that it fetches results for a task created by post_dataforseo_business_trustpilot_reviews_submit, leaving the agent to infer the workflow.

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?

With 1 parameter at 100% schema description coverage, the schema already documents the UUID id and its 30-day usability window. The description adds nothing about the parameter, so the 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?

The description states a clear verb+resource: it provides Trustpilot reviews for a business entity. It does not, however, distinguish itself from its sibling get_dataforseo_business_trustpilot_search_fetch or explain that this retrieves results of a previously submitted task (the 'by id' nature is only in the title/schema).

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?

No when-to-use guidance, no prerequisites, and no mention of the sibling submit/search tools it pairs with. The only procedural remark (checking check_url in Incognito) is about verifying results, not about when to call this tool versus alternatives.

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