load_image

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does disclose the path validation rule, which is a significant behavioral constraint, and it mentions that it 'reports metadata', hinting at the return. However, it does not mention side effects like creating a datablock, whether it overwrites existing images, or any undo behavior. This is a moderate level of transparency.

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 concise at two sentences, with the primary action stated first and the path constraint second. It is front-loaded and has no fluff. It could be improved with a clearer structure, but it is efficient and to the point.

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?

The description explains the core purpose and a key constraint, but it does not specify the exact return format (only says 'report its metadata') and lacks guidance on when to use it versus siblings. Given the tool has 5 parameters and no output schema, a bit more detail on expected outcomes would improve 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?

Schema description coverage is 100%, so each parameter already has a clear description in the input schema. The tool description adds no extra parameter semantics beyond what the schema provides. The path validation note in the description is essentially a rephrasing of the filepath schema description, so no additional value is added.

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: 'Load an image file into Blender' – a specific verb and resource. It distinguishes from sibling tools like get_image or create_image by the act of loading from disk, though it does not explicitly name any alternative. The purpose is unambiguous and easy to grasp.

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 other image-related tools (e.g., get_image, create_image). It mentions path validation but that is a constraint, not a usage condition. There is no explicit 'when to use' or 'when not to use' guidance.

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