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

With no annotations, the description carries the full burden and does add real value: it discloses per-URL independent processing with per-URL errors, and, most importantly, that credentials come from the caller's OpenAny gateway and that charges/authorization are gateway-determined — cost and auth context absent from the schema. It stops short of describing caching behavior, rendering, or failure modes beyond the generic 'errors' mention, which keeps it out of the top band.

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?

Four short sentences with no filler: scope and formats first, then batch/error semantics, then credential and billing notes. The second sentence largely echoes the urls parameter description, but the repetition is defensible as emphasis on partial-failure handling.

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?

Given a tool with a deeply documented nested body schema, no output schema, and no annotations, the description covers purpose, batch behavior, and the billing/auth model that the schema does not. Missing pieces (caching, rendering, PDF/CSV selector limits) are fully covered inside the schema, so an agent has what it needs to call the tool correctly.

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%, so the schema already explains urls, format, selectors, ttl, and conditional-request parameters in depth. The description only restates the batch size and the three output format names, adding essentially no semantics beyond the structured fields; baseline 3 applies.

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 ('Fetch content from 1 to 10 known webpage URLs') plus the three supported output formats, so the operation is unambiguous. It does not differentiate itself from siblings such as tinyfish_get or the many other URL-fetch/scrape tools in the catalog, leaving that inference to the caller.

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?

'Known webpage URLs' implicitly signals this is a fetch-by-URL tool rather than a search/discovery tool, which is useful routing context. However, there is no explicit when-to-use/when-not guidance and no named alternative (tinyfish_get, tavily_post_extract, litescrape_post_api_web_fetch) that would tell an agent which fetch tool to pick.

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