convert_file_to_markdown

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description usefully adds the constraint that the path must be absolute and visible to the server process, but it never discloses that conversion apparently runs through the markdown.new external API (per the api_key parameter), which is the key behavioral fact implied by openWorldHint.

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 tight sentences with the core purpose and the two most important constraints front-loaded; every clause carries information 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 does convey the return form ('clean Markdown text') and the supported formats, which is most of what an agent needs. It stops short of noting the external-service dependency or any failure modes for unsupported/oversized files.

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 both parameters are already documented in the schema. The description's format list (PDF, DOCX, XLSX, images, 20+ formats) is input-relevant context but not parameter-level semantics, 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?

States a specific verb (convert) and resource (local file) plus the output form (clean Markdown text). The word 'local' plus the name clearly distinguishes it from the sibling convert_url_to_markdown and convert_url_to_json tools.

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 implied by the 'local file' framing versus the URL-based siblings, but the description never explicitly says when to choose this over convert_url_to_markdown or convert_url_to_json. No prerequisites or exclusions beyond the absolute-path note.

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