Save Document

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

No annotations are provided, so the description carries full responsibility. It discloses critical behaviors: required absolute path, parent directory existence, supported formats with defaults, and Save-As-Copy behavior. However, it omits details like overwrite policy or failure modes.

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 with no wasted words. The main action is front-loaded, followed by clear constraints and options. Every sentence adds necessary information.

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 no annotations and no output schema, the description covers the tool's primary behavior, format options, and a key parameter. It is sufficient for most use cases, though it lacks details on return values or side effects like file overwriting.

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 coverage is 100%, providing a baseline of 3. The description adds value by explaining the copy parameter's Save-As-Copy behavior and listing format aliases (e.g., 'alembic' for abc). It also adds path constraints not in the schema.

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 explicitly states 'Save the active document to disk' with a specific verb and resource. It lists supported formats and explains copy behavior, clearly distinguishing the tool's purpose among siblings like open_document or import_scene.

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?

While it specifies prerequisites (absolute path, parent directory must exist) and explains the copy parameter, it does not provide guidance on when to use this tool versus alternatives such as import_scene or open_document. The context is implied but not explicit.

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