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

Annotations only declare generic flags (readOnlyHint=false, destructiveHint=true, openWorldHint=true), so the description carries the useful burden it does: the DataForSEO envelope layout (data in tasks[0].result, outcome in tasks[0].status_code), the critical fact that a rejected request still returns HTTP 200, and a per-request billing estimate. These are exactly the operational facts an agent needs and cannot get from the annotations.

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?

Front-loaded with purpose, then the envelope and sizing caveat; each sentence carries information. It is on the long side and the pricing boilerplate plus the enumeration of return fields are partially redundant against the output schema, but nothing is outright filler.

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 the return-field list is not strictly required, but the description adds the pieces it must: envelope shape, non-obvious HTTP 200 failure behavior, cost, and payload size tradeoffs. The gaps are the unaddressed input parameters and the depth instruction that has no corresponding schema control.

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% and the description never explains the input fields (keyword, language_code, location_code, location_name, location_coordinate) nor that body is an array allowing multiple tasks. Worse, it instructs the agent to choose a result-depth mode ('take regular when...') that is not present in the schema, so the guidance cannot be acted on and may 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?

States a specific verb and resource: returns the events Google surfaces for a query, synchronously, and names the returned payload fields. The resource (Events SERP) is inherently distinct from siblings like google_news_live or google_organic_live, though no sibling is named explicitly to reinforce the distinction.

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 real selection guidance for result depth (advanced is default, regular when only the ranked list matters, html only to inspect parser drops) and implies synchronous use vs task-based flows. However, that guidance refers to a depth control that does not appear anywhere in the input schema, and it never states when to call this tool instead of get_dataforseo_serp_google_events_locations or the other live SERP endpoints.

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