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

Annotations already cover the safety and idempotency profile (readOnlyHint=false, idempotentHint=true), and the description adds only 'directly' and 'one' as behavioral nuance. It does not disclose the task-based flow strongly implied by the required idempotency_key and the sibling get_pdf_task/list_pdf_tasks, so the agent must infer that conversion may be asynchronous.

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?

A single, front-loaded sentence with zero filler — verb, resource, and output format arrive in the first six words. It is efficiently structured, though slightly under-sized given it omits the async workflow context that would make it complete.

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 and both parameters are fully documented, so inputs and return values are covered. The clear gap is workflow context: the sibling get_pdf_task and the required idempotency_key suggest this initiates an asynchronous conversion, yet the description never signals that the Markdown result may need to be fetched via a follow-up call.

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 file_url and idempotency_key are already fully documented with meaningful descriptions. The tool description adds no parameter-level meaning beyond restating that a PDF or image is the input, so the baseline 3 applies.

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 specific verb (Convert), a resource (one PDF or image), and a target output format (Markdown). Naming 'Markdown' directly distinguishes it from the sibling converters convert_file_to_excel and convert_file_to_word, and 'one' sets it apart from merge_pdfs/split_pdf.

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 selection criterion is implied: use this tool when Markdown output is desired, since no other sibling produces Markdown. However, there is no explicit when-to-use or when-not-to-use guidance, and no routing to related workflow tools such as get_pdf_task for retrieving a conversion result.

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