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

No annotations are supplied, so the description carries the full disclosure burden. It states the base64 input requirement, which is helpful, but says nothing about size limits, timeout behavior, whether conversion is lossy, or what happens on unsupported/broken input — all material for an upload-and-convert operation.

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?

Two sentences, no filler, with the purpose front-loaded and the input requirement following. Slightly terse for a tool with no annotations, but nothing is wasted.

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?

With four params fully covered by the schema but no annotations and no output schema, the description should ideally explain what the conversion returns (markdown text? JSON? a file reference?) and any size constraints. It covers the input contract but leaves the output and failure behavior entirely unaddressed.

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 coverage is 100%, so every parameter including filename, file_base64, pretty_json and target_format is already documented in the schema. The description restates the base64 requirement and the default markdown target, adding no syntax, encoding variants, or valid target-format values beyond what the schema 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?

"Converteert een geüpload bestand ... naar Markdown of een ander doelformaat" gives a specific verb and resource and even enumerates the supported source formats, so an agent knows exactly what the tool does. It does not, however, say anything about the sibling tool "convert", so the agent must guess which one applies.

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?

Usage is only implied: an agent can infer the tool is for file format conversion when it holds a file's contents. There is no explicit statement of when to prefer this over the sibling "convert", no prerequisites, and no exclusions or limits on what files are acceptable.

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