备份导出全部数据

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

No annotations, so the description carries the full burden; it usefully discloses that the operation is local-only and does not upload, which is valuable for a data-export tool. However, it omits other behavioral facts such as whether existing files in the target directory are overwritten or how the result is reported.

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 sentences, front-loaded with the action and scope, and the local-only caveat placed second. No filler.

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 low-complexity, one-optional-param export tool with no output schema, the description covers purpose, scope, and the privacy-relevant local-only behavior. Only minor gaps remain (overwrite behavior, return value), which are acceptable at this complexity.

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?

The single optional parameter has 100% schema description coverage including a documented default path, so the schema does the heavy lifting. The description adds no syntax or format detail beyond what the schema already provides, so baseline 3 applies.

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: copy all local JSON data to a target directory, with the purpose (backup/migration) named. An agent can distinguish it from data_info, but it does not explicitly contrast with resume_export, the other export 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?

Gives implied usage (备份或换机迁移), which is reasonable context, but names no alternatives and no explicit when-not conditions (e.g. use resume_export for a single resume).

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