Save document

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

Beyond the annotations, it says draft saves a revision without publishing and publish makes the page live. It also notes that unsaved mutations are visible in the editor only. It does not cover failure cases, such as calling 'update' on an unpublished page, and does not describe the return value.

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?

Three sentences, front-loaded with the purpose, then the mode semantics, then usage guidance. No wasted words.

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 one-parameter save tool, the description covers purpose, mode semantics and when to invoke it. It lacks any mention of what the tool returns or how errors surface, and there is no output schema to fill that gap.

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 description for mode only repeats the enum values ('draft | publish | update'). The tool description supplies the meaning of each value, which the schema lacks.

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 says the tool saves the open document via Elementor's save commands, which is a specific verb plus resource. No sibling handles saving, so the scope is distinct from mutate_canvas and open_editor.

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 gives an explicit when-condition: save only when the user asked for it or confirmed the result. It also explains why waiting is fine, since mutations are already visible in the editor before saving. It says when each mode applies, for example 'update' for an already published page.

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