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

Annotations (readOnlyHint=false, destructiveHint=true, idempotentHint=false, openWorldHint=true) are unusual for a data-listing endpoint, and the description neither reconciles nor explains them. It adds no behavioral context such as batching, cost, timeouts, or the fact that a task ID from a prior submit is required.

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?

Two short sentences with no padding; the second sentence ('detailed overview of every resource') is mildly redundant but the description is front-loaded and easy to scan.

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?

For a POST-based task-query endpoint with rich filtering and pagination options, the description is far too thin. An output schema exists, so return values needn't be explained, but the missing prerequisite (a completed task ID), usage context, and the mismatch with the destructive annotation leave the agent under-informed.

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?

The single 'body' object param carries no description at all, and the description does not describe any parameter semantics (task id, filters, pagination, search_after_token). All meaning lives in the nested schema, which the description does nothing to reinforce or clarify.

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 names a specific verb+resource: it returns a 'list of resources, including images, scripts, stylesheets, and broken elements.' An agent can tell it retrieves crawled page resources, though it doesn't distinguish itself from close siblings like post_dataforseo_on_page_uncrawlable_resources or _links.

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 only states what the endpoint returns; it gives no when/when-not guidance, no prerequisites, and no mention of the sibling tools (e.g. _links, _uncrawlable_resources) that overlap in scope. The agent must infer usage entirely.

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