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

Annotations already declare readOnly/idempotent/openWorld, so the safety profile is covered, but the description contributes zero additional behavior — not what HTML payload is returned, not size limits, not that the result expires. The 7-day retention detail lives only in the schema, not the description.

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 short, but it is a broken placeholder sentence that carries no information and is not front-loaded with any purpose. Brevity without substance is under-specification, not conciseness.

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, but for a retrieval-by-id tool the description should at minimum state that it returns stored HTML results for a previously submitted Google Jobs task. As written, the definition is effectively incomplete.

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 100% for the single 'id' parameter, so the UUID format and 7-day reuse window are already documented in the schema. Per the baseline rule, a high-coverage schema yields 3 even with no param content in the description, which is exactly the case 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 description is a fragment — 'Description of the fields for sending a request:' — that describes nothing about the tool. The purpose is only inferable from the tool name, not the description text, and there is no differentiation from siblings like get_dataforseo_serp_google_jobs_fetch or the various *_fetch_html tools.

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 when-to-use guidance, no mention of the 7-day retrieval window as a usage constraint, and no routing versus the plain fetch sibling or the live/submit variants. Nothing tells an agent when this is the right call.

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