blender_save

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

With no annotations, the description must carry the behavioral burden. It discloses the precondition that the file must already have a filepath, which is useful, but it does not explicitly mention that the operation overwrites the current file or what happens if called on an unsaved file.

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?

The description is two short sentences, with the core action first and the prerequisite second. Every sentence earns its place with no redundant wording.

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 simple one-optional-parameter save operation, the description is largely complete: it names the action, the target, and the key precondition. It omits minor details such as return values or explicit overwrite behavior, but those are low-risk for an agent invoking this tool.

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?

Input schema coverage is 100% and the single compress parameter has a clear description. The description adds no parameter-level information, so the schema carries the meaning, matching the baseline for full coverage.

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 states a specific action (save) and resource (current Blender file), and clarifies the operation is limited to files that already have a filepath. This makes it distinguishable from the sibling blender_save_as, though it does not name that alternative 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?

The filepath prerequisite gives a clear condition for invocability but does not explicitly state when to choose this tool over blender_save_as or how to handle an unsaved file. Usage context is implied rather than spelled out.

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