Baidu Upload

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

With no annotations provided, the description carries the full behavioral burden. It does flag '(写操作)' (a write operation), which is useful, but says nothing about overwrite semantics (the conflict param silently defaults to 'rename'), whether an existing Baidu session is required, or any rate limits.

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 short sentence, front-loaded with the action and target. Nothing redundant or padded.

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 7-parameter mutation tool with no annotations, the description is too thin. Even allowing that an output schema exists (so returns need no explanation), it omits session/auth prerequisites and conflict-resolution behavior that an agent needs before invoking a destructive-capable upload.

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 86%, so the schema already documents host, port, scheme, profile, local_files and target_path. The description adds no meaning beyond the schema, which makes the baseline 3 appropriate. The undocumented 'conflict' enum (fail/rename/overwrite) is a notable gap left by both.

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 clear verb and resource: uploading local files to Baidu netdisk. This implicitly distinguishes it from the generic file_upload sibling, though it never names that alternative explicitly to confirm the boundary.

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 no when-to-use guidance, no prerequisites (e.g. must be logged into Baidu), and no indication of when to prefer this over file_upload or baidu_download. Nothing routes the agent among the many baidu_* siblings.

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