Convert File

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

Annotations provide only idempotentHint and openWorldHint, and the description adds no behavioral detail beyond the verb 'Convert'. It does not state whether the source file is modified, whether network access is needed (though source_url implies it), or any side effects. Since the description contributes nothing beyond the annotations, the transparency burden is largely unmet.

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 short sentence that is efficient and front-loaded with the verb 'Convert'. However, it is so under-specified that it borders on generic, listing input categories but no output formats, examples, or usage context. It earns its place as a minimal statement of purpose but lacks informative structure.

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 a rich schema (all parameters documented) and an output schema, the description needs only to provide overarching context and selection guidance. It fails to provide selection guidance or mention that target_format is required, relying on the schema for that. The coverage is adequate for basic invocation but incomplete for choosing among siblings.

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 each parameter already has a clear description. The tool description itself adds no parameter-level detail and does not clarify how filename, source_url, file_base64, or source_format interact. Per the baseline rule for high schema coverage, a score of 3 is appropriate.

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 a clear verb ('Convert') and lists input types (document, spreadsheet, presentation, image, PDF, or data file), which conveys the general purpose. However, it does not distinguish this generic converter from specialized siblings like images_to_pdf, compress_pdf, or extract_pdf_text, so it lacks explicit differentiation.

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?

There is no guidance on when to use convert_file versus any of the sibling tools. The description does not mention preferred scenarios, prerequisites, or exclusions, leaving an agent to infer usage purely from the schema. This is a significant gap given the crowded sibling set.

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