convert_to_markdown

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals a side effect: 'Automatically logs token savings to a local database' and exposes a dashboard URL. However, it does not specify the return format (e.g., whether Markdown is returned as a string or written to a file), nor does it mention dependencies like Tesseract installation or network access for URLs, leaving some behavioral ambiguity.

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 concise sentences, front-loaded with the core purpose. Each sentence contributes distinct information: purpose, supported formats, side-effect/logging, and invocation instruction. There is no filler or redundancy.

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?

This is a simple one-parameter tool, but without an output schema, the description should clarify what the conversion produces. It fails to state whether the Markdown is returned inline, saved to a file, or delivered via the dashboard, and doesn't mention input size limits or error conditions. The logging side effect is disclosed, but the absence of return semantics is a notable gap.

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 already describes the 'input' parameter as 'Absolute file path or HTTP/HTTPS URL to convert' with 100% coverage, giving a baseline of 3. The description adds value by enumerating supported file types and noting that images use OCR, clarifying valid input categories beyond the generic path/URL description.

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 clear verb and resource: 'Convert a file or URL to Markdown.' It enumerates supported input types (PDF, DOCX, PPTX, XLSX/XLS, images with OCR, web pages), making the purpose unambiguous. Even without siblings, the scope is specific and distinct.

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 implies when to use the tool by listing supported formats and instructs to 'Pass an absolute file path or an HTTP/HTTPS URL.' It lacks explicit exclusions or alternative tools, but the supported-format list provides clear context for typical conversion tasks.

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