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

With no annotations carrying the burden, the description is unusually transparent: it states output size thresholds, inline text vs base64/downloadUrl behavior, bearer-token reuse, the 10 MB input limit, and the per-page credit cost of deepRead. This gives an agent accurate expectations before calling.

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 four dense sentences with no filler: it front-loads the action, then follows with input constraints, output behavior, size limits, and deepRead cost in logical order. Every sentence earns its place.

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 7-parameter tool with no output schema and no annotations, the description covers input modes, limits, output delivery, authentication-sensitive download behavior, and optional AI deep-read cost. Combined with full schema coverage, an agent has everything needed to invoke the tool 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?

Even though schema coverage is 100%, the description adds meaningful relationships beyond the terse schema: base64 and url are alternatives, `from` is inferred from filename/URL extension, deepRead means OCR+layout understanding with credit cost, and output representation depends on format and size. These clarifications materially improve parameter understanding.

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 opens with a specific verb and resource: 'Convert a file', and the surrounding detail makes clear this is the execution tool for conversions. It is distinguishable from the check/get/list siblings by intent, but it never explicitly names or contrasts those siblings.

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 gives strong invocation guidance: provide base64 OR a public URL, omit `from` when an extension is present, keep files under 10 MB, and use deepRead for scans/photos/handwriting. However, it does not explicitly say when to choose convert_file over the sibling tools like check_conversion or get_conversion.

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