render_image

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

With no annotations, the description carries the behavioral burden. It discloses the important side effect that output is written to disk, restricts input to self-authored markup, and sets expectations with 'Not photorealistic.' It does not describe overwrite behavior or return values, but the essential operational behavior is transparent.

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 two sentences with no wasted words. It front-loads the primary action and resource, then provides use cases and a limitation in a tightly packed second sentence.

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?

For a 6-parameter tool with no annotations and no output schema, the description plus schema is mostly sufficient: an agent can call it with just source and rely on defaults. However, it does not clarify what happens after rendering (returned file path? generated filename?) and does not mention how width/height or output_format influence the result, leaving some uncertainty.

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 only 33%, so the description needed to compensate for width, height, format, and output_format. It usefully connects source content to the format enum ('SVG markup' vs 'full HTML document'), but does not explain output_format, filename, or dimension semantics beyond what the schema already provides.

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 concrete verb ('Render'), names the accepted source types ('SVG markup or a full HTML document'), and states the output ('image file on disk'). It clearly distinguishes itself from siblings like render_video and list_providers, and adds a boundary with 'Not photorealistic.'

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?

It explicitly lists intended use cases: illustrations, diagrams, charts, UI mockups, typographic cards. It also provides an exclusion with 'Not photorealistic,' but it does not explicitly contrast with render_video or list_providers, so an agent is left to infer the alternative use cases.

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