load_image

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action but does not disclose whether the image is embedded, linked, or referenced, whether existing images with the same name are replaced, or what happens on invalid file paths. For a tool that mutates the blend file, this is a significant gap.

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 front-loads the core action. It earns its place with no filler, though it could add a bit more useful context without becoming bloated.

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 has an output schema and two parameters, the description is too thin. It does not explain the 'name' parameter, the return value, or behavioral details like file format support or overwrite semantics. An agent would likely need to inspect the schema and guess at the tool's behavior.

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?

Schema description coverage is 0%, so the description must compensate. It mentions 'filepath' implicitly via 'from file' but does not explain the 'name' parameter at all, nor does it clarify the expected filepath format or supported image formats. The description adds minimal meaning beyond the schema's bare parameter names.

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 verb ('Load') and resource ('an image from file into the blend file'), which clearly distinguishes it from sibling tools like render_image or import_file. It is clear but does not explicitly differentiate from the broader import_file sibling, so it loses one point.

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 context: loading an image asset into the current blend file, as opposed to rendering or importing other file types. However, it does not explicitly state when to use this tool versus alternatives like import_file or list_images, nor does it mention any prerequisites or exclusions.

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