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

The annotations declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, but the description frames the tool as simply providing citation data, implying a safe read operation. It gives no warning about destructive behavior or side effects, directly contradicting the destructive annotation.

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?

The description is a single front-loaded sentence with no wasted words. However, it is too terse for a complex POST endpoint with many nested parameters and filters, making the brevity feel under-specified rather than optimally concise.

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 a complex content-search endpoint with a required request body, pagination, filtering, and destructive annotations, the description omits all usage, behavioral, and parameter context needed for correct invocation.

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 sole top-level parameter is a body array with 0% top-level schema description coverage. The description mentions only "target keyword" and does not explain the body array structure, required keyword/offset_token alternatives, filters, pagination, or other nested fields, leaving the parameter largely uncontextualized by the description.

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 a specific action and resource: it provides detailed citation data for a target keyword. It is clear enough to understand the tool's core purpose, but it does not distinguish this endpoint from related DataForSEO content-analysis siblings such as sentiment analysis or content summary.

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 guidance on when to use this tool instead of alternatives, no prerequisites, and no exclusions. The agent has no indication of appropriate contexts or limits beyond the terse purpose statement.

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