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

Annotations declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, but the description is silent on any of this behavior nor on the task-based workflow. It also omits the non-obvious prerequisite that a task must first be created via the Task POST endpoint, whose ID is what the request actually carries.

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?

A single tight sentence with no filler, so nothing is wasted. It is arguably under-specified rather than concise, but structurally it is clean and front-loaded.

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, and the requirement lift is low. Still, the description omits the task-creation workflow that governs this call, which is the main context an agent would need to invoke it correctly on the first try.

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 schema description coverage reported at 0% for the top-level `body` parameter, the description needs to compensate, and it does not. Saying 'the page you indicate in the request' gestures at a URL but says nothing about the required task `id` that the body actually requires.

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 HTML of a page'), which is clear enough for an agent to select it. However it makes no attempt to distinguish itself from close siblings such as post_dataforseo_on_page_content_parsing, post_dataforseo_on_page_resources, or post_dataforseo_on_page_page_screenshot, all of which operate on the same target page.

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 prerequisites, and no mention of alternatives among the many OnPage siblings. An agent gets a purpose and nothing about selection criteria.

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