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

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuinely useful behavior: the call runs two-stage via the DataForSEO API (implying latency/external dependency) and the returned HTML is truncated to max_bytes in UTF-8 bytes. It doesn't mention failure behavior for unreachable URLs, but the added context is well beyond the 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?

Three short sentences, purpose front-loaded, with the truncation and workspace caveats following. Nothing is redundant, though the phrasing is dense German and could be marginally tighter.

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 no explanation, and the annotations cover the safety profile. For a simple 3-parameter read tool, what's given is nearly sufficient; only explicit sibling routing is missing.

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 coverage is 0%, so the description must carry the load — and it explains max_bytes as a UTF-8 byte truncation limit and workspace as a customer-workspace slug that is optional when only one workspace exists. Only 'url' is left self-explanatory, which is reasonable.

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+resource ('Rohes HTML einer URL') plus a concrete use case (JSON-LD-/Markup-Checks im Quelltext), which separates it from parsing/crawl siblings like dfs_content_parsing or dfs_onpage_instant. It never names those alternatives explicitly, so differentiation is implicit rather than stated.

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?

The parenthetical use case implies when this tool is appropriate, and the workspace note covers a setup precondition. There is no explicit 'use X instead when...' routing or statement of when this tool is the wrong choice versus other DataForSEO endpoints.

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