Save Drawing

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

With no annotations beyond the title, the description must disclose behavioral traits. It states 'Save the current drawing' but does not clarify whether this overwrites the existing file, creates a backup, or if it requires a prior save. It fails to explain the destination when no path is given (current path). The destructive nature is implied but not explicit.

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 concise with two sentences. It is front-loaded with the primary action. However, it could be slightly more precise without significant verbosity, e.g., specifying that it overwrites the existing file unless a new path is given.

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?

Given the presence of many sibling tools, no output schema details, and the simplicity of the tool, the description is too minimal. It does not mention return values (despite an output schema existing), error conditions, or the impact of saving (e.g., it may finalize the drawing state). For a potentially destructive operation, more context is needed.

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%, with the path parameter fully described. The description adds minimal value beyond the schema: 'Optionally specify a new path' paraphrases the schema. It does not explain what happens when a new path is given (e.g., changes the drawing's current path or just exports a copy), missing an opportunity to clarify behavior.

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 'Save the current drawing' with a specific verb and resource. However, it does not distinguish from the sibling tool 'drawing_save_as', as both allow specifying a new path. The phrase 'Optionally specify a new path' creates ambiguity about whether this changes the current file's path or just saves a copy.

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 provided on when to use this tool versus alternatives like 'drawing_save_as' or 'drawing_close'. There is no mention of prerequisites, such as the drawing needing a path already set, or when not to use it. The description lacks any context for appropriate usage.

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