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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds useful behavioral context: the cost ratio ($0.002 vs $0.012) and the response envelope structure (tasks[0].result, status_code, HTTP 200 on rejection). However, the core behavior described (returning job listings) is misaligned with the intended purpose (locations), so transparency is incomplete.

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 is not overly long, but the first sentence is confusing and adds noise. The cost and envelope details are useful and could be retained. The structure could be improved by front-loading the actual purpose (list of locations) rather than the misleading job listings phrase.

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?

The description fails to explain that this tool returns a list of location codes for Google Jobs, which is its core purpose. It lists output fields but doesn't clarify their meaning in the context of locations. The output schema exists but the description doesn't connect it to the intended use. An agent would be uncertain about what data to expect and how to use it.

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?

With zero parameters, the schema is empty and the description does not need to explain any parameters. The baseline of 4 applies; the description adds nothing about parameters but also doesn't 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?

The description states 'Returns the job listings Google surfaces for a query on Google' which contradicts the tool name and title indicating it should return a list of locations for Google Jobs. It lists SERP fields (keyword, item_types, etc.) that are typical of a search result, not a location list, making the purpose vague and potentially misleading.

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?

No guidance is provided on when to use this tool versus alternatives like get_dataforseo_serp_gads_advertisers_locations or get_dataforseo_serp_google_events_locations. There is no mention of use cases, exclusions, or how it differs from sibling location tools.

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