save_blend

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

With no annotations provided, the description carries full behavioral burden. It states the action but fails to disclose important behavior: saving the current file overwrites the existing file (destructive), and does not describe what happens on invalid paths, error handling, or whether the operation is reversible. The description is minimal and does not prepare the agent for consequences.

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 a single, concise sentence that is front-loaded with the primary action and immediately clarifies the two modes. There is no wasted wording or redundant detail; every word earns its place.

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 the tool's simplicity (one optional parameter) and the existence of an output schema, the description is reasonably complete, but it omits critical context such as overwrite behavior, error outcomes, and whether the operation is reversible. A save operation with potentially destructive overwrite deserves more explicit caveats. The minimalism creates a 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 has zero descriptions for the 'filepath' parameter, so the description must compensate. It adds useful semantics by specifying that the path must be an 'explicit absolute path', and implies that a null value saves the current file. However, it does not detail format requirements, validation, or behavior beyond that. This is a partial compensation for the 0% schema 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 clearly states the tool's verb ('Save') and resource ('.blend file'), and distinguishes two distinct behaviors: saving the current file or saving a copy to a specified path. This is specific and unambiguous, and it is naturally distinct from the sibling tools (which are inspection, animation, rendering, etc.).

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 description does not provide any guidance on when to use this tool versus alternatives. It mentions two modes (save current vs. save copy) but does not explain when to choose one over the other, nor does it mention any prerequisites, side effects, or exclusions. No alternatives are referenced.

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