format_convert

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

No annotations exist, so the description must handle transparency alone. It only states basic conversion without disclosing traits such as validation behavior, error handling, lossiness, or transformation assumptions. This is insufficient for an agent to anticipate side-effects or constraints.

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?

Description is a single efficient sentence with no redundant words. It immediately conveys the core operation and supported formats.

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?

No output schema and no annotations. Description omits critical details like return format (e.g., plain string, object) and does not address error scenarios (e.g., unsupported conversion direction). For a conversion tool, this leaves the agent guessing about what the output looks like.

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?

Input schema covers 100% of parameters with descriptions; the tool description adds no additional meaning beyond the schema. Baseline score of 3 applies as the description does not enhance parameter understanding.

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?

Description clearly states verb 'Convert' and resource 'document formats' with explicit list of formats (Markdown, HTML, XML, JSON). It differentiates from sibling tools like docx_to_html or html_to_markdown by being a general converter among these four formats, though it does not explicitly contrast with specific siblings.

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?

No guidance is provided on when to use this generic converter versus format-specific sibling tools (e.g., html_to_markdown). The description lacks any 'use-if' or 'prefer-alternative' hints, leaving the agent without decision support.

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