load_image

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the action and purpose. It does not say whether loading replaces the current image, whether it has side effects, what happens with invalid paths, or what the output contains. 'Load' implies reading an existing file, but that is minimal.

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?

A single sentence that is front-loaded with the verb and object. It contains no filler and communicates the core purpose efficiently.

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?

For a simple one-required-parameter tool with an output schema, the description is minimally adequate: an agent knows what to do and what input to provide. However, in the context of many sibling tools, it lacks guidance on workflow placement and how this load differs from other loading/opening operations.

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 coverage is 100%, and the path parameter is already described as 'Path to the image file to load.' The description adds little beyond the schema, so the baseline of 3 applies. It confirms the parameter refers to an existing file, but no format or sourcing details are 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 uses a specific verb and resource: it loads an existing image file for annotation. This makes the tool's purpose immediately clear and distinguishes it from siblings that create images (capture_screenshot), list them (list_images), or retrieve them in other forms (get_image).

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?

No guidance is provided about when to use this tool versus alternatives such as get_image, open_in_preview, or list_images. The phrase 'for annotation' implies its context, but it does not state exclusions, preconditions, or how to obtain a valid path.

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