krita_set_diffusion_region

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

Beyond the annotations, it discloses meaningful behavior: removal destroys region/controls but not artwork, ambiguous links are rejected, an active Generate document is required, operation_id should be reused, and there is no guaranteed undo. This is exactly the kind of context an agent needs beyond readOnly/destructive/idempotent hints.

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 compact and front-loaded with the primary action. Every sentence carries distinct information, and there is no repetition of schema titles or obvious filler.

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 covers preconditions, parameter semantics for prompt/remove, side effects, and a failure mode. However, with no schema property descriptions and no output schema, key required IDs remain unexplained and the result of the operation is unspecified. It is adequate but leaves visible gaps.

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 must compensate. It clarifies positive_prompt ('required unless removing') and remove ('remove region and its controls'), and node_id is implied as the target layer. However, instance_id, operation_id, and document_id are left undefined, so agents cannot confidently map those required parameters.

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 opens with specific verbs and a concrete resource: 'Create/update a prompt region linked directly to an existing paint/group layer, or remove that region and its controls without deleting artwork.' This clearly identifies the operation and distinguishes it from generic diffusion controls or layer deletion siblings.

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 gives clear contextual guidance: a prompt is required unless removing, an active Generate document is required, and ambiguous/multiple links are rejected. It does not explicitly name alternative tools or state when not to use it, but the context is sufficient for most routing decisions.

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