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

The description adds rich operational context far beyond the annotations: byte-size measurements for the three depth options, cost per call, and the envelope contract—'data in tasks[0].result', with 'a rejected request still returns HTTP 200'. This gives the agent concrete expectations about size, cost, and failure semantics that the annotations do not cover.

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 front-loads purpose and response fields, then condenses depth choice and cost into compact, decision-relevant sentences. Some numbers are repeated (e.g., the 57 KB measurement appears twice) and the envelope detail appears late, but every sentence does earn its place.

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 an output schema present and annotations supplied, the description is nearly self-sufficient: it covers what the tool returns, the three depth modes, pricing, and envelope/error behavior. The remaining gap is the undocumented request body, which matters given it is the sole required parameter.

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 description coverage is 0%, so the description carries the burden, but it never explains the body parameter shape: that it is an array of task objects with only keyword required, nor the meaning/selection of location_code, language_code, or coordinate fields. The only request-behavior hint is 'Wrapped in DataForSEO's envelope', which describes response structure, not input semantics.

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 line, 'Returns the events Google surfaces for a query on Google, synchronously,' states a specific verb, a specific result type (events), and synchronous delivery. This is enough to distinguish it from siblings like post_dataforseo_serp_google_organic_live or post_dataforseo_serp_google_maps_live without opening their schemas.

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?

The description gives explicit decision rules for choosing between result depths: 'advanced is the default choice; take regular when only the ranked list matters and html only to check what the parser dropped'. It also frames cost/position relative to the family ('this family is the cheapest source of search data here'), though it does not name an alternative tool for a different SERP type.

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