convert_file

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

Since no annotations are provided, the description takes full responsibility for behavioral traits. It details performance ('Fast'), security ('fully local - the file never leaves the machine'), and functional quality (preserving tables, headings, lists).

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 information is highly condensed and logically ordered: function, capabilities, detailed features, and critical constraint (locality). It achieves maximum information density with minimal waste.

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?

Despite lacking an output schema, the description is extremely complete. It defines the input scope, output format (clean Markdown), and critical behavioral guarantees (preservation of structure and local operation).

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 coverage is 100%, meaning the input schema is perfectly described. The description does not add semantic meaning to the 'path' parameter beyond the file type and local constraint, meeting the baseline for high schema coverage.

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 purpose is perfectly clear: convert a local document file into 'clean Markdown.' It specifies the exact action and the desired output format, distinguishing it from generic conversion 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?

The description clearly specifies the context of 'local document file' and its 'fully local' nature. This acts as a strong usage guideline, helping the agent choose this tool over remote or API-based conversion siblings.

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