Krita Open File

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

No annotations are provided, so the description must carry the full behavioral burden. It only states the action and supported formats; it does not disclose whether opening a file replaces the current document, what happens with unsaved changes, or how missing/invalid paths are handled.

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 short sentence that is front-loaded with the action and resource, and every word adds value. The supported-format list is compact and useful without bloating the text.

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 one-parameter file-opening tool, the description is minimally sufficient: it names the operation and accepted formats. However, because there are no annotations and no guidance about replacing the current document or error behavior, it leaves some operational uncertainty.

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 schema has 0% description coverage, so the description needs to clarify the 'path' parameter, but it only lists file extensions. It does not explain whether the path should be absolute or relative, accepted URI forms, or what happens if the file cannot be found. The parameter name is self-evident, but no additional meaning is provided.

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 ('Open') and resource ('a file in Krita'), and lists common formats, making the tool's purpose immediately clear. It is distinct from siblings like krita_new_canvas and krita_save, so an agent can tell them apart without inspecting schemas.

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 intended use is implied: load an existing Krita-compatible file. However, the description does not explicitly state when to use this tool versus creating a new canvas or saving, nor does it mention any preconditions or alternatives.

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