Analyze domain overview

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

Annotations only declare readOnlyHint=false, openWorldHint=true, destructiveHint=false. The description adds the substantive behavioral facts an agent needs: an API write scope is required, a cache miss can consume the project's own DataForSEO budget, every call requires an explicit cost cap, and fresh never removes that cap. That is exactly the kind of cost/auth context annotations cannot carry.

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?

Four sentences, all earning their place, with the budget/scope warning front-loaded. Dense but not redundant; a little more framing on what the report contains would improve readability.

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 compensates by sketching the three possible return shapes (estimate, cached report, charged report). Combined with the cost-cap and scope guidance, an agent has enough to call it correctly, though the composition of the report itself is only loosely described.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning on top: it explains the estimate_only + max_cost_cents=0 pairing for a free estimate and clarifies that fresh bypasses cache without lifting the cost cap. These cross-parameter interactions are not spelled out in 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?

The description conveys that this is the paid Domain Overview analysis that returns an estimate, a cached report, or a report with charged keyword and page module outcomes, which is a specific verb+resource. It stops short of naming the sibling tools (estimate_domain_overview_cost, load_domain_overview_keywords/pages) that a reader would compare against, so differentiation is implied rather than explicit.

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?

It gives a concrete recommended workflow: call with estimate_only=true and max_cost_cents=0 first for a free estimate, and notes fresh=true bypasses cache. It does not explicitly say when to prefer estimate_domain_overview_cost or the load_domain_overview_* readers over this tool, so exclusions are absent but the context is clear.

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