krita_create_document

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

Annotations already provide readOnlyHint, destructiveHint, and idempotentHint, lowering the bar. The description adds useful constraints beyond annotations: the 16-megapixel limit, the RGBA/U8/sRGB format, and the active view requirement. It does not detail destructive consequences, but the annotation covers that.

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?

Two short sentences with the core action front-loaded and the retry note as a separate useful piece of guidance. No filler or redundant wording.

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 5 required parameters, no output schema, and no per-parameter descriptions, the tool needs more context about how instance_id and operation_id are used and what the result looks like. The description is too thin to guarantee correct invocation in all cases.

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 needed to explain all five parameters. It only touches on operation_id with 'Reuse operation_id on retries,' giving a hint about retry behavior. Width, height, name, and instance_id are not described at all, though some are self-explanatory.

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 operation: creating a new bounded RGBA/U8/sRGB document with an active view. It distinguishes this from sibling tools like open_document, activate_document, or list_documents by specifying the creation verb and resource characteristics.

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 given on when to use this tool versus alternatives such as krita_open_document or krita_import_image_layer. The only usage note about reusing operation_id on retries addresses idempotency, not tool selection.

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