Close Drawing

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

Beyond the destructiveHint annotation, the description discloses the default save behavior, that the drawing is saved to its current path, and that the drawing session becomes unusable until drawing_new or drawing_open is called. This gives the agent a clear mental model of the state transition.

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?

Two sentences, front-loaded with the core action, and every sentence adds essential information: what happens, what the default does, and what must happen next.

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 a single optional parameter, an output schema, and a destructiveHint annotation, the description fully covers the tool's behavior, parameter semantics, and postcondition. No important calling context is missing.

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?

The schema already documents save with a default and description, but the prose adds behavioral detail: save=true triggers saving to the current path before closing. This adds value beyond the schema's one-line parameter description.

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 specific verb and resource: 'Close the current drawing.' It clearly differentiates from siblings like drawing_open, drawing_save, and drawing_save_as by focusing on the closing action and the resulting session state.

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 states the required next action after closing ('you must call drawing_new or drawing_open before any other tool'), which is strong context for sequencing. It does not explicitly contrast with save-only alternatives, but the close/save distinction is implied by the save parameter and sibling names.

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