save_design

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true, and openWorldHint=false. The description usefully clarifies the semantics behind that: it writes a NEW version to Fusion's cloud rather than overwriting locally, which is meaningful context. It still says nothing about auth requirements, failure modes, or what the destructive hint actually destroys.

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 front-loaded sentence with no filler. The verb, resource, and output location all appear immediately.

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?

Annotations cover the safety profile and there is no output schema to explain, so the core is adequate. However, for a mutation tool with one undocumented parameter, the definition omits both the meaning of that parameter and any sense of what a successful save returns or requires.

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% for the single 'description' parameter, and the description text never mentions it or its default value. The description therefore fails to compensate for the schema gap, leaving the agent to guess that 'description' is a version annotation rather than, say, a design 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?

States a specific verb (Save) and resource (the active document) with the precise scope of the write: a new version in the cloud. This is clear enough that an agent can distinguish it from close_design or new_design, though it does not explicitly name a sibling to contrast against.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The phrase 'the active document' implies it applies to whatever design is currently open, but that is inference rather than stated guidance, and it is silent on preconditions (e.g., whether an active design must exist).

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