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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower, yet the description adds genuinely useful behavior: the DataForSEO response envelope (data in tasks[0].result, outcome in tasks[0].status_code) and the key fact that a rejected request still returns HTTP 200. That error-handling detail is exactly the kind of signal an agent needs and cannot get from 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?

It is front-loaded with the purpose sentence followed by the envelope explanation, which is good ordering. However, the long enumeration of return fields (keyword, se_domain, check_url, spell, refinement_chips, ...) duplicates what the existing output schema already provides, and the pricing comment block is cosmetic boilerplate that does not help invocation.

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?

For a no-parameter endpoint with an output schema and full annotation coverage, the description does supply the envelope and billing context. But the central claim — that it returns SERP items for a query — conflicts with the name/title and the empty schema, leaving the agent unclear on what the call will actually produce.

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 per the baseline a 4 applies; with nothing to document there is no semantic gap to compensate for. The description appropriately does not invent parameters.

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 says it returns the events Google surfaces for a query, but the tool name and title describe a list of Google Events *locations*, and with zero parameters a query-driven SERP fetch is not possible. The stated verb+resource is clear in isolation but misaligned with the tool's own identity, so an agent cannot reliably tell what this endpoint actually returns.

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 statement of when to use this endpoint versus the obvious sibling post_dataforseo_serp_google_events_live, nor versus the other *_locations enumerations (e.g. get_dataforseo_serp_google_jobs_locations). The agent must infer usage entirely on its own.

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