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

The description is candid operationally (50304, no tasks array, HTTP 200, measured date), but annotations mark destructiveHint=true while the description presents a read-style count operation and even says the Reddit server reads the platform directly. Since the description contradicts the destructive annotation rather than reconciling with it, the contradiction rule caps this dimension at 1.

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?

Despite its length, every sentence adds value: purpose, availability status, failure signature, envelope behavior, and an alternative. The key warning is front-loaded immediately after the purpose statement, and no filler is present.

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 output envelope and top-level failure mode are fully specified, so an agent can detect 50304 even though HTTP status is 200. Given an output schema exists, return-value documentation is unnecessary, and the alternative tools are named; the definition is complete for operational use.

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%, the description needed to explain the body shape; it only echoes `targets` without clarifying the array-of-objects wrapper, the required absolute-URL format, the 10-target maximum, or the per-URL charge. The nested schema provides those details, but the description itself adds minimal parameter semantics beyond naming the key field.

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 first sentence states a concrete contract: 'return Reddit sharing counts for `targets`'. This clearly names the verb, resource, and input scope, and the member name plus sibling list distinguishes it from the other DataForSEO business tools. The intended behavior remains unambiguous even though the endpoint is currently unavailable.

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 description explicitly warns that the endpoint is 'currently unavailable upstream' and gives the exact failure signal, so an agent knows not to rely on it. It then names the working Pinterest sibling and the direct Reddit source as alternatives, which is more explicit routing than most tool descriptions provide.

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