upload-file-for-conversion

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

With no annotations provided, the description carries the full burden. It discloses that the tool 'provides specific upload instructions and explains how to handle local files with remote servers,' which adds useful behavioral context about its instructional nature. However, it lacks details on permissions, rate limits, or error handling, leaving gaps for a mutation tool.

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 concise and front-loaded, with two sentences that directly address purpose and usage. Every sentence adds value without waste, making it efficient and well-structured for an AI agent.

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 no annotations and no output schema, the description is moderately complete. It covers the core use case and behavioral intent but lacks details on return values, error conditions, or security aspects. For a tool with 3 parameters and mutation implications, it should do more to compensate for missing structured data.

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 100%, so the schema already documents all parameters well. The description adds no specific parameter semantics beyond what's in the schema, such as explaining the 'tool_type' enum or 'local_file_path' usage. Baseline 3 is appropriate as the schema does the heavy lifting.

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 purpose: uploading local files for conversion when they don't exist on the server. It specifies the verb ('upload') and resource ('local file'), but doesn't explicitly differentiate from sibling tools like the direct conversion tools (pdf-to-markdown, etc.), which presumably handle files already on the server.

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 usage guidance: 'Use this tool when you need to convert a local file that doesn't exist on the server.' It distinguishes this from alternatives by implying that sibling tools (e.g., pdf-to-markdown) are for server-side files, though it doesn't name them directly.

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