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

Annotations already cover safety (readOnlyHint true, destructiveHint false, openWorldHint true), so the bar is lower, and the description still adds real behavior: parallel execution, per-URL failure isolation (one bad URL does not abort the batch), optional BM25 lexical selection, and preservation of complete Markdown code/table blocks. It also flags a trust boundary for web content, which is valuable for an open-world read tool.

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, front-loaded sentences with no filler, and the core capability leads. The semicolon-telegraphic style and unexplained jargon ('lexical BM25 selection') keep it just short of ideal.

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, open-world batch extractor with no output schema, the description covers execution semantics and the untrusted-content caveat, which is the important part. It falls short on parameter-level guidance for a 7-parameter tool and gives no return-shape expectations (e.g., per-URL success/error structure) despite advertising per-URL failure isolation.

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 only 29% across 7 parameters. The description hints at the 'query' parameter's lexical BM25 selection and the markdown default's code/table preservation, but force_refresh, request_budget, chunks_per_source, and max_characters are not explained beyond the two that carry schema descriptions, leaving several parameters opaque.

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 ('extract URLs') plus distinctive scope ('concurrently', 'isolates failures per URL'), so the agent knows it is a bulk multi-URL extractor. However, it never distinguishes itself from the near-identical sibling deepseek_fetch, so an agent choosing between the two gets no help from the text itself.

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?

There is no explicit when-to-use statement and no mention of the siblings deepseek_fetch or deepseek_search, even though 'fetch' overlaps heavily with 'extract'. The concurrency/per-URL failure isolation implicitly suggests batch use, but the agent must infer that rather than being told.

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

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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld), so the bar is lower. The description still adds real value by disclosing the return shape — raw provider Markdown plus provenance and truncation metadata — which matters because there is no output schema. It omits caching behavior implied by force_refresh.

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?

A single sentence with zero filler, front-loading the action ('Fetch one public webpage') and then the result payload. Every clause earns its place.

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?

With no output schema, the description correctly carries the return-value burden, and annotations handle safety. However it leaves force_refresh and the 8192-char URL constraint unexplained and gives no guidance on retry/budget behavior, so an agent can call it but cannot fully reason about its parameters.

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 only 50%: max_characters and request_budget are documented in the schema, but url and force_refresh have no description anywhere. The description mentions 'truncation metadata' but never explains force_refresh's cache-bypass semantics, which is the least obvious parameter an agent must set.

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 one public webpage') plus the provider, and the 'one ... webpage' scope implicitly separates it from a multi-result deepseek_search. It does not explicitly name or differentiate itself from deepseek_extract, so sibling routing still requires inference.

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?

Usage is only implied: you have a single URL and want its content. There is no statement of when to prefer this over deepseek_extract or deepseek_search, nor any prerequisites (e.g. publicly reachable, no auth-protected pages) beyond the word 'public'.

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

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds the 128-character native query limit, which is genuinely behavioral, but says nothing about retries (despite the request_budget param), caching, or how need_content/force_refresh change behavior.

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 tight sentences with the core purpose front-loaded, then syntax support, then the length constraint and routing hint. No filler, though the operator list is dense enough that a second read is needed to map operators to parameters.

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 16-parameter tool with 19% schema coverage and no output schema, the description leaves most of the surface undocumented — notably the boolean/output-shaping params (need_content, force_refresh, max_characters, request_budget) and additional_queries. An agent can form a basic query but cannot confidently use the majority of the tool's capabilities.

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 only 19%, so the description must compensate, and it partially does by mapping operator syntax to parameters (site:/-site: → include/exclude domains, after:/before: → date range, quotes/OR → query semantics). However, roughly ten parameters (count, max_results, need_content, force_refresh, localization, ori_question, additional_queries, include_text/exclude_text, max_characters) get no explanation of purpose or interaction.

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 ('DeepSeek native web search') and the query syntax it supports, which sets it apart from deepseek_fetch/deepseek_extract as a query-based search tool. It does not explicitly name those siblings, but the resource is unmistakable.

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?

Gives a concrete switching rule: native queries are capped at 128 Unicode characters, so use 'advanced' for longer queries and filters. That is a clear when-to-use-this-vs-other condition, though it references a tool not present in the sibling list and never mentions when to prefer deepseek_fetch or deepseek_extract.

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