deepseek_fetch

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

With no annotations, the description carries full behavioral burden. It usefully discloses the output form (markdown) and that crawling is done by DeepSeek's official crawler, but omits auth requirements, rate limits, JS-rendering behavior, and failure modes on non-HTML or unreachable URLs.

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 tight sentences with the primary action front-loaded and the usage hint second. No filler, though the second sentence is somewhat marketing-flavored ('Ideal for deep-dive reading').

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 simple 2-parameter fetch tool with a complete schema and no output schema, the description covers the essentials. It is adequate but thin on behavioral details (truncation interaction with max_length, error behavior) that an agent would benefit from.

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 both parameters (url, max_length) are fully documented in the schema. The description adds no syntax, format, or default detail beyond what the schema already provides — baseline 3.

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 ('Fetch and extract') and resource ('readable Markdown text of a specific webpage'), and identifies the mechanism (DeepSeek's official crawler). It implicitly contrasts with deepseek_search by framing itself as the follow-up read step, but never explicitly differentiates from the sibling.

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 an intended-use context ('deep-dive reading on search results or analyzing documentation from a specific URL'), which implies the fetch-after-search workflow. However, it never names deepseek_search as the alternative or states when NOT to use it.

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