export_image

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

No annotations are provided, so the description carries the full burden. It does disclose one genuine behavioral trait — the output format is inferred from the file extension — but says nothing about what happens when output_path already exists and overwrite is false, permissions, or whether the session is mutated.

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?

A single efficient sentence with the core action and the format-selection behavior front-loaded. No filler, though it is short enough that the missing guidance is conspicuous rather than trimmed.

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?

An output schema exists, so return values need not be explained, and the mutation nature is clear from 'Export'. However, for a write-to-disk tool with zero annotations and undocumented overwrite semantics, the description should address file-collision and session-state requirements.

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% for 3 parameters. The description adds real meaning for output_path (its extension determines the encoded format), which is more than the bare schema, but session_id and especially overwrite (default false, unclear collision behavior) are left undocumented.

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?

States a specific verb (Export) and resource (the session) plus the target artifact (image in PNG/JPEG/WebP/other GIMP format). It does not explicitly differentiate itself from the sibling document_save_as, which is the nearest ambiguity, so it falls short of a 5.

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?

There is no guidance on when to choose this over document_save_as or any other sibling, no prerequisites, and no note about requiring an open/active session. Usage must be inferred entirely from the name and the word 'session'.

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