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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals essential traits: conversion to Markdown, a comprehensive list of supported formats, the requirement for an absolute path, and a maximum file size. While it doesn't detail error handling or edge cases, it provides enough practical behavioral context for an agent to select and invoke the tool safely.

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 a single, focused paragraph that front-loads the primary purpose, then delivers format support, a path requirement, and size limit—all in compact, useful sentences. No wasted words, and the structure is easy to scan.

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?

The tool supports many formats and has an output schema present, so the description needn't detail return values. It covers the key operational aspects: what it converts to, which inputs are supported, the path format, and a size constraint. It could mention error behavior or archive handling nuances, but overall it is complete enough for an agent to use effectively.

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 only one parameter (file_path) with 0% description coverage, so the description must compensate. It does so by specifying 'Provide the absolute file path' and listing supported formats, which effectively constrains what the parameter should contain. This adds meaningful guidance beyond the raw schema.

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 clearly states the verb 'Convert' and the resource 'a local file to clean AI-ready Markdown'. It explicitly lists supported formats, which distinguishes it from sibling tools like convert_url, convert_arxiv, and convert_youtube that handle remote sources. The purpose is unambiguous and specific.

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 provides clear context: use this tool for local files, and the supported format list implies when it should not be used (unsupported types). It instructs users to 'Provide the absolute file path' and notes the 20MB limit. It does not explicitly name alternatives like 'use convert_url for online content', but the local-file emphasis and sibling context make the usage clear.

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