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

Goes well beyond the readOnly/openWorld annotations: it discloses that content is not truncated by the server, the return shape, billing at 5 CNY per 1,000 successful fetches, and a 25 QPS rate limit. Those cost/throughput facts are exactly the operational context annotations cannot carry.

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, each doing a job: what it does, what returns, validity constraints, cost/rate. Nothing is padded, though the URL constraints duplicate the schema rather than adding value.

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?

There is no output schema, and the description compensates by describing the returned object's fields and the no-truncation guarantee. Cost and rate limits round out everything an agent needs to call this predictably.

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% and the single `url` parameter is already fully documented in the schema (absolute HTTP/HTTPS, no credentials, maxLength 8192). The description restates the same constraints without adding format examples or edge-case handling, so this is textbook baseline territory.

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 a URL through DeepSeek') and says what comes back (raw JSON with title and Markdown content). The one blemish is the title saying 'as Markdown' while the body says 'raw JSON', which could briefly confuse, though the body reconciles it. It does not contrast with the `search` 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?

The description gives hard input constraints (absolute HTTP/HTTPS, no credentials, 8192 chars) but never says when to reach for this tool versus `search` or when not to use it. An agent is left to infer that this is for a known URL rather than discovery.

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 only cover readOnly/openWorld; the description adds real operational context the agent cannot otherwise know: billing (5 CNY/1,000 requests producing results), a 100 QPS rate limit, and the fact that results are neither filtered nor truncated server-side. It also warns that need_content output can be very large.

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?

Well front-loaded — what it is, what comes back, the key flag, then syntax and billing. Dense with no filler, though the response-field list and syntax list make it longer than strictly necessary since the schema already repeats the query syntax.

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 an 11-parameter, no-output-schema search tool, the description covers return shape (results array with named fields), size risk, cost, rate limits, and syntax. Nothing an agent needs to call this correctly 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 still adds value by documenting DeepSeek query-syntax support and by clarifying a cross-parameter behavior not visible in the schema: structured filters are appended to the query string.

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 ('Search the web with DeepSeek's search API') and specifies the return contract ('raw JSON response exactly as received'). It also distinguishes itself from the sibling by naming 'fetch' for single-URL retrieval.

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?

Explicitly routes single-URL needs to the 'fetch' tool and gives a condition for need_content ('can be very large'). It stops short of describing when *not* to use search at all, but the alternative framing is clear enough to guide selection.

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