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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses that failed fetches appear in failed_results[] rather than raising an error, warns the agent to read that array, and provides measured latency. This is meaningful behavioral context an agent needs before calling.

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?

The description front-loads the core purpose, then uses bolded array names and short clauses to cover return behavior, failure handling, performance, and sibling alternatives. Every clause earns its place with no filler.

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 read-only extraction tool with a rich output schema, the description provides purpose, response shape, failure semantics, performance expectation, and sibling routing. Nothing needed for correct invocation 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 100%, so the baseline is 3. The description restates that urls is required and can take several URLs, and points to format and extract_depth, but it does not add much semantic detail beyond the schema's already complete parameter descriptions.

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 explicitly says it fetches clean, parsed content for URLs you already have, naming the specific resource and use case. It is immediately distinguishable from post_tavily_search, post_tavily_map, and post_firecrawl_batch_scrape.

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?

It gives a clear when-to-use rule ('whenever you can already name the pages'), an explicit alternative to avoid (post_tavily_search), and concrete handoffs to post_firecrawl_batch_scrape for long lists and post_tavily_map for site discovery. This fully routes an agent among siblings.

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