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

Annotations exist but are generic (readOnly false, destructive true, openWorld true), and the description adds nothing beyond them — no note that this is a billed live POST task, no rate/cost context, no pagination hints despite limit/offset params. It also does not resolve the tension that this is a data-retrieval endpoint annotated as 'destructive'.

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. It is appropriately sized, though arguably too terse for the amount of behavior it should disclose.

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 described, but for an endpoint with a rich body object of filters, sorting, and ranking options, the one-sentence description leaves the agent without enough context on invocation behavior.

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?

Only one top-level parameter (body) with 0% schema description coverage at that level, and the description says nothing about it beyond 'the target you specify.' The many nested optional fields (filters, order_by, backlinks_filters, etc.) are left entirely to the schema.

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-resource pair: it returns an overview of 'referring IPs and subnets pointing to the target.' The mention of IPs/subnets implicitly separates it from the sibling referring-domains endpoint, but it never names or contrasts with that sibling explicitly.

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 guidance on when to choose this over post_dataforseo_backlinks_referring_domains_live or the other backlink endpoints, and no prerequisites (auth, task cost, target format) are stated. Usage must be inferred entirely from the tool name.

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