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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so "Reads only" is redundant. The description does add genuine behavioral context the annotations cannot: which DataForSEO account a lookup would draw from, the remaining budget, that prices carry a read-date, and that a budget is charged per lookup. It does not say whether this requires an active workspace context or what happens when no DataForSEO account is connected.

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 lead clause is well front-loaded, but everything after it is a single comma-chained run-on spanning seven distinct payload areas, which makes it harder to scan than a short bulleted or sentence-per-topic structure. Each item does carry information, so nothing is padding, but the packing hurts usability.

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 no output schema, the description carries the full burden of describing return values, and it does so thoroughly — account source and rationale, budget, per-request and per-keyword pricing with read date, worst-case cost for 100–1,000 keywords in two currencies, lookup types, languagesByCountry, row limits, and the difficulty formula. The remaining gap is operational: no guidance on when to call it or how it relates to the research tools it is meant to precede.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter claims are made that could mislead.

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 opening clause "How keyword research runs for this workspace" plus the enumerated contents (account selection, budget, pricing, lookup types, row limits, difficulty formula) make it unmistakably a configuration/introspection tool rather than a research tool. It never names a sibling such as get_keyword_research or research_keywords, so the agent must infer the boundary itself.

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 explicit when-to-use statement, no prerequisite, and no named alternative. The natural use case — checking budget and per-keyword pricing before calling lookup_keyword_volumes or research_keywords — is left entirely to inference, and "Reads only" signals safety rather than timing.

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