convert_md_to_jpeg

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the high-level conversion and does not mention whether an output file is always written, what happens when output_file is omitted, whether existing files are overwritten, or how mermaid diagrams inside the markdown are handled.

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 clean sentence with no filler, so it is concise and front-loaded. It is slightly under-sized for a tool with six parameters and a sibling, but conciseness itself is strong.

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?

Without annotations or an output schema, the description should compensate by explaining invocation behavior, output defaults, and limitations; it does not. An agent cannot tell what happens when output_file is optional or whether mermaid diagrams are processed, leaving important operational gaps.

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 100%, so all six parameters already carry their own descriptions. The tool description adds no additional parameter meaning, but with complete schema coverage the baseline of 3 is appropriate.

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 uses a clear verb and resource: converting a markdown file into a JPEG image. It distinguishes itself from the sibling convert_mermaid_to_jpeg by naming markdown as the input, though it does not explicitly contrast the two 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?

No guidance is given about when to choose this tool over convert_mermaid_to_jpeg or when it would be inappropriate. The only implied usage signal is the phrase 'markdown file', which is not explicit enough to count as clear context or exclusions.

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