deepseek_fetch

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.