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

Adds substantial context beyond the annotations: the DataForSEO envelope layout (tasks[0].result vs tasks[0].status_code), the fact that a rejected request still returns HTTP 200, per-item size (~7.7 KB), and pagination via search_after_token. The annotations carry the safety profile and the pricing note explains the billing side effect, so this is strong but not exhaustive.

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?

Purpose is front-loaded, followed by pagination, size, the target-type warning, and the envelope note. Most sentences earn their place; the pricing boilerplate block is noise but is tooling-inserted rather than authored.

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?

For a complex, many-parameter, billed search call, the description covers the high-risk pitfalls (target shape, envelope, error-as-200, pagination) and an output schema exists so return values need not be re-explained. It could say more about non-target params, but nothing essential for a correct call is missing.

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?

Coverage is reported at 0%, so the description must compensate. It does this for the critical parameter by warning that target is an array of objects ({domain}/{keyword}) and that a bare string or array of strings is rejected, plus a pointer to the filter-field source. The remaining params (platform, location, language, order_by, limit) are left to the schema's own nested text.

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 resource and verb: the individual answers where an assistant mentioned your target. It names the sibling it is not (aggregated_metrics for counts), so an agent can distinguish 'raw mentions' from 'counts' without opening either 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?

Explicitly routes to post_dataforseo_ai_llm_mentions_aggregated_metrics_live when counts rather than mentions are wanted, and points to get_dataforseo_ai_llm_mentions_available_filters for filter fields. It also says to page with the token rather than offset past the first pages. It doesn't differentiate from the other mentions siblings (top_domains, top_pages, cross_metrics), so it falls short of a full 5.

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