blender_save_blend

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

Annotations already state readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds behavioral details beyond annotations: the fallback to current file/temp location and relative path resolution against the working directory. It does not contradict the annotations and provides useful side-effect information.

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 sentences long and front-loads the core purpose: 'Save the current scene as a .blend file.' The subsequent sentence provides two necessary clarifications about path behavior. Every word earns its place; no redundant or filler content.

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 save tool with one optional parameter, the description sufficiently covers the action, fallback behavior, and path resolution. It omits nothing critical that would prevent correct invocation, and the output schema likely documents the return value, so the description need not explain it.

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 only defines 'path' with a default of null and no description (0% schema description coverage). The description compensates fully by explaining what happens when the path is omitted and how relative paths are resolved, giving complete meaning to the single parameter.

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 action with a specific verb and resource: 'Save the current scene as a .blend file.' This distinguishes it from sibling tools like blender_export_stl (which exports a different format) and various validation/rendering tools. The output format is explicit.

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?

Provides clear context on path behavior: explains what happens when path is omitted (saves to current file or temp location) and how relative paths are resolved (against MCP server's working directory). It does not explicitly name alternatives, but there is no comparable save tool among siblings, so exclusions are unnecessary.

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