save_active_drawing

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

No annotations, so the description carries the full behavioral burden. It usefully discloses that this is a write to the existing path (no Save-As dialog, no new file), but says nothing about what happens for an untitled/never-saved drawing, whether the call can fail, or what it returns on success.

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 sentence with no padding, and the key constraint ('existing path') is placed where it is read first. Nothing is wasted.

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?

For a 0-param, no-output-schema tool this is nearly complete: the action and its write target are clear. The only gap is unsaved-drawing behavior and success/failure signaling, which matters slightly more here because no annotations declare the safety profile.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a 0-param tool applies. The stated path behavior is the only semantic an invocation needs.

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 (save) and resource (active drawing) with a scoping detail - 'to its existing path' - that implicitly separates it from create_drawing_copy. An agent can tell what it does without opening the schema, though no sibling is named explicitly.

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?

Usage is implied: persist edits to the currently open drawing without choosing a new location. There is no explicit when-to-use/when-not framing and no named alternative (e.g., 'use create_drawing_copy to save elsewhere') to route the agent.

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