convert_eml

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

With no annotations, the description carries full burden. It discloses the return value (Markdown with front matter), the optional disk write, and the behavior of presets and flag overrides. However, it does not explain the thread_mode and thread_order parameters, leaving some behavioral aspects unexplained.

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 concise with six sentences, front-loaded with the core action, and uses a clear bullet-like list for presets. Every sentence adds value without repetition or fluff.

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?

Given the tool's complexity (14 parameters, presets, output schema), the description covers the main purpose, return value, presets, and override logic. It lacks explanation for thread_mode and thread_order, but overall provides sufficient context for most use cases.

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 0%, so the description must add meaning. It explains presets and mentions several flags (signatures, tracking pixels, etc.), and notes that individual flags override presets. However, it omits details for thread_mode, thread_order, and some boolean flags. The presets bundling compensates partially.

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 tool converts .eml to Markdown with YAML front matter, specifying the output format and the optional file write. It implicitly distinguishes from siblings like convert_directory and convert_eml_to_bundle by focusing on a single file conversion.

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 guidance on preset usage and flag overrides, but it does not explicitly state when to use this tool versus sibling tools like convert_directory or convert_eml_to_bundle, which would help an agent choose correctly.

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