save_xcf

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

No annotations are provided, so the description carries the burden for behavioral disclosure. It adds the critical detail that existing files require overwrite=true, implying the default behavior will not overwrite and may fail. However, it omits other behavioral traits such as whether saving marks the image as clean, or any details about return values or errors, which would be useful given the lack of annotations.

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, front-loaded sentence that efficiently conveys the core function and the key overwrite guardrail. Every word contributes value, with no waste or repetition.

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?

The tool is simple, but the description is minimal. It covers the essential purpose and the overwrite caveat, but does not mention sibling tools for comparison, nor does it elaborate on parameter usage beyond overwrite. Given the absence of annotations, a more complete description would include guidance on alternatives or expected path format, making this adequate but not exceptional.

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 compensate for parameter meaning. It only clarifies the 'overwrite' parameter, leaving 'image_id' and 'path' unexplained. Though the parameter names are somewhat self-explanatory, the description does not specify the expected format for path (e.g., whether to include the .xcf extension) or how to obtain image_id. This is insufficient given zero schema descriptions.

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's function: 'Save an image as XCF'. This is a specific verb + resource combination, and the mention of XCF distinguishes it from sibling tools like export_image, which presumably handles other formats.

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 no guidance on when to use this tool versus alternatives. The only usage hint is the overwrite condition, which is parameter-specific, not a tool-selection guideline. Siblings like export_image and open_image are not mentioned, so the agent receives no explicit direction on choosing save_xcf.

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