convert_pdf

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

No annotations are provided, so the description carries the full disclosure burden. The operation list gives a high-level sense of behavior, but it does not disclose side effects, file overwriting behavior, output handling, permissions, or return values. For a multi-operation tool this is a significant gap.

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 compact and front-loads the scope ('PDF 专用操作') before listing the supported operations. There is minimal waste, though the list is dense and could benefit from grouping or formatting to aid scanning.

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?

This tool has nine distinct operations, nested options, no annotations, and no output schema, so the description needs to explain more than just the operation list. Missing details include per-operation prerequisites, how options map to operations, output behavior, and expected results, making the definition incomplete for reliable invocation.

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 input schema already provides descriptions for the top-level parameters and the nested options, with roughly 80% coverage. The description adds no parameter-specific meaning beyond naming operation types, so it does not substantially improve on what the schema already 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 states clearly that this is a PDF-specific operation tool and enumerates nine supported operations, so an agent can understand the tool's core purpose. It distinguishes itself from general conversion siblings by focusing on PDF manipulation, but it does not explicitly contrast with similar tools like convert_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 phrase 'PDF 专用操作' implies this tool should be used for PDF-specific tasks rather than general format conversion. However, there is no explicit guidance about when to prefer this over sibling tools, nor any prerequisites or exclusions for individual operations.

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