MiConvert File Converter

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

Goes well beyond the annotations by disclosing the actual mechanics: server downloads the file, returns a download link valid roughly 4 hours, and may complete synchronously or asynchronously with a job_id. Annotations only cover readOnly=false, openWorld=true, idempotent=false, and destructive=false, so this operational detail is genuinely additive.

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?

Three dense sentences, front-loaded with capability, then constraints, then the async escape hatch. Every clause carries information an agent needs and there is no filler.

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 no output schema, the description carries the return-value burden and does so: it names the download link, its ~4 hour validity, and the processing/job_id alternative outcome. Size limit, reachability requirement, and the async path cover everything needed to invoke it correctly.

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% and each of the four parameters is already documented, so the baseline is 3. The conversion examples implicitly clarify what 'to' and 'from' accept, but the description adds no explicit guidance on the optional filename or on when 'from' is required beyond what the schema states.

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?

States a specific verb and resource ('Convert a file') and immediately scopes it to 'from a public URL to another format,' with concrete conversion pairs (OFD→PDF, HEIC→JPG) that make the tool's domain unmistakable. The async handoff to get_conversion_status further distinguishes it from its sibling.

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?

Gives clear triggering context and constraints: the file must be publicly reachable, capped at 50 MB, and the caller is told to use get_conversion_status with the returned job_id when the result is 'processing'. It does not mention list_supported_formats as a way to discover valid target formats, which would have made the routing complete.

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

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

Beyond the readOnlyHint and openWorldHint annotations, it discloses the key behavioral trait that this call blocks for roughly 25 seconds before returning. It does not say what the response looks like or which error appears if the job times out, leaving that part of behavior unexplained.

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 short sentences, with the purpose first and the latency caveat second; nothing is redundant or padded.

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 no output schema, the description carries the burden of explaining return values, and it does name the download links for the completed case. It omits what a still-processing or failed result looks like, which is a modest gap for a single-parameter polling tool.

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 has full coverage for the single job_id parameter and already states it comes from convert_file, so the description adds no meaning beyond that and only repeats the same origin.

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 pairs a specific verb and resource ('Check a conversion started by convert_file') with the outcome ('get its download links once complete'), which clearly distinguishes it from its sibling convert_file.

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?

It states the precise condition for calling it: a conversion started by convert_file that was still processing. It stops short of saying what to do if the job is still running after the wait, so the polling loop is left implicit.

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

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered. The description still adds valuable behavioral detail beyond them by explaining exactly what the response varies on — target formats for a given source, or the full set of source formats when omitted — which is what an agent needs to interpret the result.

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?

Three short sentences with zero filler: the purpose comes first, the mode behavior second, the usage rule last. Every sentence contributes information an agent needs to select and call the tool.

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 single-optional-parameter read-only tool with no output schema, the description covers purpose, mode behavior, and follow-up workflow. The only soft gap is that it does not say whether formats are returned as bare extensions or with human-readable labels, but that is minor given the tool's simplicity.

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 the baseline would be 3, but the description earns more: it clarifies that `from` is a source format that pivots the output to target formats, and that omitting it changes the result set entirely. The schema only says "Source format extension... Optional" and never describes that output-shaping effect.

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 names a specific verb and resource ("List the formats MiConvert converts between") and then precisely differentiates the two operating modes of the tool: with `from` it returns targets for that source, without it returns every source. An agent can immediately tell this is the capability-discovery tool rather than a conversion executor like convert_file.

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?

It gives an explicit usage rule: "Use it to check that a conversion exists before calling convert_file," which names the relevant sibling and the precondition it serves. It does not state any when-not-to-use condition, but for a read-only lookup tool there is little ambiguity to resolve beyond that.

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