wps_wpp_export_pdf

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

With no annotations, the description fully discloses critical behavioral traits: WPS is sandboxed to ~/Downloads or the original directory, exports to other paths return 'success' without creating a file, and no error is surfaced at the object model level. It also notes the tool does not guarantee path validity. This is exemplary transparency.

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 somewhat long, but every sentence adds value—purpose, sandbox restriction, failure mode, and verification advice. It is front-loaded with the main action and then provides necessary caveats without unnecessary fluff.

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?

Given the complexity of sandbox restrictions and silent failures, this description covers the main purpose, critical constraints, failure behavior, and post-action verification. It is fully sufficient for an agent to use the tool safely despite lacking an output schema or annotations.

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 schema only says 'path' is an optional export path, but the description adds crucial semantics: the path must be in ~/Downloads or the document's original directory, otherwise silent failure occurs. This guidance directly enriches understanding of the parameter beyond the schema description.

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 clearly states the action: '把当前演示文稿导出为 PDF' (export the current presentation to PDF). This is a specific verb+resource+output format, and it distinguishes from sibling wps_word_export_pdf by specifying '演示文稿' (presentation) vs. document.

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 provides explicit guidance: strongly recommends exporting to ~/Downloads ('强烈建议导出到 ~/Downloads') and warns against unauthorized paths that will be silently blocked. It also instructs to verify the file after export, which is critical for correct usage.

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