save_blend

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

The description discloses the behavior when filepath is omitted (saves over current file or uses temporary path and returns it). This adds value beyond a basic description, though it does not cover error cases or return success/failure.

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 short and well-structured: one purpose sentence followed by a parameter block. Every sentence adds necessary information without redundancy.

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 single parameter, no output schema, and no annotations, the description covers the essential behaviors. It could be improved by mentioning overwrite behavior or error handling, but it is largely complete for its simplicity.

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?

With 0% schema description coverage, the description fully compensates by explaining the filepath parameter's meaning, providing an example, and detailing the two possible behaviors (with path vs. omitted). This adds significant semantic value.

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 ('Save') and the resource ('the current Blender project as a .blend file'). It uses a specific verb and resource, and effectively distinguishes this tool from siblings like load_blend.

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 implies usage (to save a Blender file) but does not explicitly state when to use it versus alternatives. No exclusion or alternative tool is mentioned, although the sibling list contains load_blend which is complementary.

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