load_image

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only restates the purpose and fails to disclose behavioral traits such as how name conflicts are handled, whether the image references the file or is packed, or what happens when the filepath is invalid. This is a significant gap for a tool that mutates the blend file.

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?

Single sentence of eight words, front-loaded with the verb and object. No redundancy, no wasted words. Perfectly sized for a tool with minimal parameters.

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?

With 2 parameters, no annotations, and 0% schema coverage, a one-sentence description is insufficient. The ambiguous 'name' parameter and lack of duplicate/error behavior leave an agent without enough information for correct invocation. The presence of an output schema partly mitigates return-value uncertainty, but input behavior remains underspecified.

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%, and the description adds no parameter semantics. The 'name' parameter's behavior (e.g., data-block name, derived from filename when null) is undocumented in both schema and description. Only 'filepath' is self-evident from the tool name.

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 uses a specific verb ('load') with a clear resource ('image from file') and destination ('into the blend file'). It distinguishes itself from siblings like load_file (loading a whole blend file) and import_file (external format import) by specifying it loads an image asset into the current Blender file.

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 provides no guidance on when to use this tool versus alternatives such as import_file, load_file, or list_images. No exclusions, prerequisites, or context are given.

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