Save Drawing

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

Annotations provide only the title, so the description carries the full burden of behavioral disclosure. It states the save operation but does not disclose overwrite behavior, whether the current file is replaced, what happens if the file already exists, or whether the operation is destructive. For a mutation-like operation, this is a meaningful gap.

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 short sentences with no filler. The core action is front-loaded, and the only parameter-related detail is stated efficiently. Every sentence earns its place.

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?

This is a simple one-parameter tool with an output schema, so the description does not need to explain return values. However, the lack of differentiation from drawing_save_as and the absence of any mention of overwrite or default-path behavior leave the description slightly incomplete for an agent selecting between sibling tools.

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% for the single 'path' parameter, so the schema already documents its behavior well. The description adds the phrase 'specify a new path,' which is mildly useful but largely redundant with the schema's 'Optional save path; uses current path if omitted.' This matches the baseline for high schema coverage.

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 action ('Save the current drawing') and the optional path parameter. However, it does not explicitly differentiate this from the sibling drawing_save_as, which appears to serve a very similar purpose when a new path is specified.

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 use drawing_save versus drawing_save_as, nor any mention of what happens when omitting the path versus specifying one. The phrase 'Optionally specify a new path' actually blurs the line with drawing_save_as, so an agent cannot confidently decide which tool to invoke based on the description alone.

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