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

The description frames the tool as pure data retrieval ("provide you with data"), while annotations declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false. Nothing in the text reconciles this, and no other behavioral traits (task queuing, per-call cost, live-vs-cached behavior) are disclosed.

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 zero filler or repetition. It is efficient, though the terseness here reflects under-specification rather than disciplined economy.

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. But for a live POST endpoint with a rich nested filter/body structure and destructive/readOnly ambiguity, one sentence leaves the agent without enough to call it correctly or safely.

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?

Top-level schema description coverage is 0%: the single required `body` array is undocumented at that level. The description only gestures at "the indicated date range," adding no meaning about keyword format, date_group, rank_scale, search_mode, or the filter syntax beyond what the (admittedly detailed) nested item schema already supplies.

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?

"Provide you with data on all citations of the target keyword" names a resource (keyword citations) and a scope (date range), so it is not a tautology. However, it never mentions trends, phrase trends, or the fact that this is a content-analysis endpoint, so it does not differentiate itself from siblings like post_dataforseo_content_search_live or post_dataforseo_content_sentiment_analysis_live.

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, when-not-to-use, or alternative-tool guidance. The only contextual hint is "for the indicated date range," which describes scope rather than selection criteria, leaving the agent to guess between this and the other content_*_live endpoints.

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