batch_convert_documents

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

Annotations are absent, so the description must disclose behavioral traits. The description only states the action and does not mention any side effects, permissions, error conditions, output behavior, or potential to overwrite files. This lack of disclosure leaves the agent without critical information about the operation's consequences.

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, concise sentence that directly states the tool's purpose. There is no redundant or excessive wording, making it efficient and front-loaded.

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 tool with four parameters, nested options, and no annotations or output schema, the one-line description is insufficient. It does not specify supported formats (though in schema), how batch processing behaves, or what the return value represents. The tool is moderately complex, and the description leaves many behavioral and contextual gaps.

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 covers 75% of parameters with descriptions, and the options object has nested descriptions for its fields. The description does not add any information about parameters such as output format or paths, but the schema already provides sufficient semantic context. Since the schema does most of the heavy lifting, the description's lack of parameter details is acceptable.

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 tool's function: batch conversion of multiple documents. The verb 'convert' and resource 'documents' are specific, and the word 'batch' distinguishes it from the sibling tool convert_document, which likely handles a single 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 implies the tool is for converting multiple documents at once, but it does not explicitly state when to use this tool over alternatives like convert_document for single documents or when not to use it. There is no mention of prerequisites or exclusions, so the usage guidance is only implied.

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