Baidu Share Save

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that this is a write operation, but omits other important traits: authentication requirements, whether the save is asynchronous, overwrite/conflict behavior, rate limits, and what happens to existing target directory contents.

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?

The description is a single short sentence with zero wasted words and the operation type front-loaded. However, for a 9-parameter write operation, such extreme brevity likely sacrifices necessary structure and detail.

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 and schema coverage is high, so parameter and return-value details are documented elsewhere. But with no annotations and a complex 9-parameter write operation, the description is not complete enough: it lacks prerequisites, auth context, and operational behavior such as async task handling.

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 89%, so the input schema already documents nearly all parameters in detail. The description only restates the share-link source and target drive conceptually, adding no syntax, format, or constraint information beyond what the schema provides.

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?

The description gives a specific verb and resource: '转存分享链接内容到网盘' (save shared-link content to cloud drive), and explicitly flags it as a write operation. It implicitly distinguishes from siblings like baidu_copy, baidu_upload, and file_share_add by focusing on saving content from a share link, though no sibling is named directly.

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?

Only the parenthetical '(写操作)' indicates the operation type. There is no guidance on when to choose this over baidu_copy, baidu_upload, or other baidu_* tools, nor any prerequisites such as needing a valid share URL or extraction code.

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