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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety behavior is covered by structured data. The description adds only a mild behavioral note that output is scoped to the location/keyword from the POST request, and omits richer context such as the 30-day id validity (which the schema carries) or result-retrieval semantics. With annotations covering the safety profile, a 3 is appropriate.

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?

Two sentences, front-loaded with the endpoint purpose, but the second sentence is largely boilerplate about location/keyword scoping and adds little actionable value. It is not bloated, but no sentence is maximally earning 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?

An output schema exists, so return values need not be explained. However, for a fetch-by-id tool in a submit/fetch pair, the description omits the critical workflow context (that the id originates from the submit sibling and that results are time-limited), leaving the agent to infer the async pattern from the title and schema alone.

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?

There is a single parameter (id) with 100% schema description coverage, so the schema fully documents it as a UUID task identifier usable for 30 days. The description adds no additional parameter meaning beyond the schema, which is the expected baseline of 3 when the schema does the heavy lifting.

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 it returns Tripadvisor business data, which is a clear enough resource, but it never articulates that this is an async fetch-by-task-id endpoint. It does not differentiate itself from the sibling post_dataforseo_business_tripadvisor_search_submit or the reviews fetch tools, so an agent cannot confidently pick it over alternatives from the text alone.

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 explicit when-to-use guidance. The mention that results are 'specific to the location... and keyword parameters used in the POST request' hints at a submit/fetch pairing but never states that this tool should be called after submitting a task or that the id comes from that submission. No exclusions or prerequisites are given.

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