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

Annotations already declare destructiveHint=true, openWorldHint=true, and non-idempotent, which is the counterintuitive part an agent most needs warned about. The description adds nothing beyond that profile — no mention that this is a live, credit-consuming request or how the body array is processed.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though for an endpoint of this complexity the brevity edges toward under-specification rather than elegant concision.

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?

With 10+ nested request fields and an output schema handling return values, the description should still cover usage context and the array-wrapped body shape. As written, an agent learns nothing about request structure, routing versus siblings, or operational cost.

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 `body` wrapper parameter is undocumented in the description, so the agent gets no signal that input must be an array of task objects rather than flat fields. The nested schema fields (target, filters, order_by, rank_scale, etc.) are thoroughly described in the schema itself, which partially compensates.

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 ('provide') and resource ('referring domains') scoped to 'the target you specify', so the core purpose is clear. However, it does no sibling differentiation, which matters here because several siblings (post_dataforseo_backlinks_bulk_referring_domains_live, referring_networks_live, get_semrush_referring_domains) cover closely adjacent ground.

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 conditions, and no mention of alternatives among the ~30 sibling tools. The agent must infer from the name alone whether this is the right tool versus the bulk or network variants.

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