download_official_file

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

Annotations only tell the agent it is a non-readOnly, open-world, non-idempotent, non-destructive call. The description goes well beyond them by disclosing concrete side effects: writes into downloads/, records a SHA-256 manifest, deliberately skips extraction, and caps download size at 8 GiB. It omits what happens when the target file already exists, leaving the overwrite parameter's effect unexplained.

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: the first gives the action and its side effects, the second gives the hard limits. No filler, and the most decision-relevant facts (no extraction, size cap) are up front.

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?

An output schema exists so the manifest result needs no prose, and the destructive/size behavior is covered. Still, for a 4-parameter, 3-enum tool with zero schema documentation, an agent cannot tell what 'complete' vs 'core' costs in size or what overwrite=true does, which the description should fill in.

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 0% and the description offers no parameter guidance at all beyond hinting that selection is per manifest item. Vocabulary like dataset=core vs complete, the ten file_category values, and the non-idempotent overwrite flag are left entirely to inference from bare enum members.

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?

Specific verb (下载) plus a precisely scoped resource: a .7z file from RegNetwork's official download page, written to downloads/ without extraction. An agent knows exactly what the call produces. It does not name a sibling (export_network, get_database_status) to contrast against, so it stops short of 5.

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 implies when the tool applies (pulling official published datasets rather than querying the live graph), and it adds a real usage constraint: one official manifest item per call, max 8 GiB. It never states when not to use it, nor points to a sibling for the alternative path of getting interaction data.

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