create_blend

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

The description explains the core behavior (creates and saves a .blend file, optionally running a script, with compression). However, it does not disclose important side effects like potential file overwriting, error handling for invalid paths or templates, or authentication/authorization requirements. Since no annotations exist, the description carries the full burden, but it only partially fulfills it.

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 extremely concise: one sentence for the purpose followed by a compact, well-structured Arg block. Every line adds value, no redundant text, and the key action is front-loaded. It is an optimal length for quick reading.

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?

Considering no output schema or annotations, the description covers the essential inputs and outputs. It explains parameters well but omits what the tool returns (e.g., success indicator or file path) and does not mention error conditions (e.g., overwrite behavior, invalid template). These gaps are minor for a creation tool but prevent full completeness.

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 Arg section adds rich semantics to all four parameters: clarifies path is relative/absolute and appends '.blend', enumerates template values, explains script runs bpy code after template, and defines compress. Given 0% schema description coverage, the description fully compensates, making each parameter's meaning clear.

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 first sentence clearly states the action ('Create') and resource ('.blend file from a starter template and save it'). It distinguishes the tool from siblings like render, inspect_blend, and run_script by focusing on creation of a new file, which is unique among the listed sibling tools.

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 lacks explicit context such as 'use this to start a new project' or 'for modifying existing files, use add_reference or run_script'. The agent is left to infer usage solely from the name and brief purpose.

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