download_fulltext

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

Goes beyond the annotations (which only flag openWorldHint=true, readOnlyHint=false) by disclosing concrete operational traits: a 100MiB size cap, per-redirect validation, and the refusal to handle authentication, paywalls, or login pages. These are real constraints an agent must plan around; only the return/failure behavior is left unstated.

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 tightly packed sentence front-loads the core action and follows with constraints. No filler or redundancy; every clause adds an actionable fact.

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 network-fetch tool with no output schema, the description covers the safety-relevant constraints well, but leaves unanswered what gets returned, what happens on failure/redirect exhaustion, and how the downloaded file is bound to work_id. Adequate but not complete.

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 0%, so the description carries the full burden. It partially covers 'url' (must be HTTPS, public, size-capped) but says nothing about what 'work_id' is for or how the two parameters relate. With both parameters required and undocumented, a key gap remains.

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: downloading a PDF from a public HTTPS URL. It scopes the source clearly (user-selected, public, HTTPS) which distinguishes it from sibling file-ingest tools like parse_local_pdf or import_document, though it never names an alternative explicitly.

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 negative scope ('不处理账号、付费墙或登录页') gives an implicit when-not condition, and '用户选定的公开HTTPS地址' implies the intended trigger. But there is no positive routing guidance telling the agent when to choose this over import_document or parse_document.

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