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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so safety is covered. The description does add genuine DataForSEO-specific behavior: the tasks[0].result / tasks[0].status_code envelope and the fact that a rejected request still returns HTTP 200. However, that behavioral detail is framed around returning job-listing items rather than locations, so it partly describes the wrong operation.

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 envelope sentence is compact and front-loaded, but the long enumeration of return fields is largely redundant with the existing output schema and, given the tool mismatch, is likely wasted or misleading text. Size is acceptable; relevance is not.

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 return values need not be explained, yet the description spends most of its length doing exactly that while never clarifying what a 'locations' call actually yields or how it differs from the jobs fetch/submit siblings. For an endpoint whose whole purpose is the location list, the description leaves the core question unanswered.

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 schema has zero parameters, so per the calibration baseline the schema itself is trivially complete and there is no parameter meaning for the description to supply. The field list in the description refers to return values rather than inputs, limiting its usefulness here.

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 tool name and title say it lists Google Jobs *locations*, but the description says it 'Returns the job listings Google surfaces for a query on Google' and enumerates item-level result fields (items, item_types, items_count). That describes the sibling fetch tool, not a locations-lookup endpoint, so the stated purpose is misleading relative to the tool's own identity.

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 when-to-use guidance, no mention of prerequisites (this is a zero-parameter lookup), and no routing to or away from the many sibling locations/fetch/submit tools. The agent gets no help deciding when this tool applies.

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