Utils Doc Convert

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds useful payment/route context ('POST /v1/utils/doc-convert', '0.10 USD x402...'), but says nothing about conversion behavior, input requirements, output characteristics, or limits beyond the price.

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 short, but the first line merely restates the title and the second line is route/payment metadata. It is under-specified rather than appropriately concise, and the useful payment context is not preceded by a clear statement of what the tool does.

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?

An output schema exists, so return values need not be explained here, but the description is still missing core context: purpose, parameter meaning, usage conditions, and operational behavior. It provides only route and price metadata, which is not enough for an agent to invoke the tool confidently.

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 0%, and the description does not explain either parameter. It never clarifies that 'to' likely means target format or that 'text' is the input content, so it adds no semantic meaning beyond the bare schema property names.

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 essentially repeats the title/name 'Utils Doc Convert' and adds a route/payment line. It does not state what is converted, what document types are supported, or how this differs from sibling tools such as v1_utils_translate_doc. This is close to tautology rather than a clear verb+resource purpose.

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 this tool, when not to use it, or which sibling tool to choose instead. The description only gives a remote route and price, leaving all usage decisions to inference.

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