apply_fill_preset

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

No annotations are provided, so the description carries the full burden. 'Apply' signals a mutation that presumably overwrites existing fill settings, but the description never says what prior state is replaced, whether presets must pre-exist, or whether permissions/resources are required. Only the 'named preset' phrasing hints at a dependency.

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?

One efficient sentence with no padding, and the action is front-loaded. Its problem is under-specification rather than verbosity, which caps it at adequate.

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?

An output schema exists, so return values need not be described, but for a 3-parameter mutation tool with zero annotation coverage and zero schema descriptions the definition leaves too much unknown. An agent cannot tell what uid refers to or what applying a preset does to current fill state.

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% across three parameters, so the description must compensate and largely doesn't. It only implies that 'preset' is a name; 'uid' (which object type?) and the optional 'channel' (what a channel selection does here) are completely unexplained.

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 definition names a specific verb+resource (apply a named preset) and enumerates the source kinds it targets: Fill, Fill Effect, Generator, Filter. That distinguishes it from apply_baking_preset and apply_smart_mask in the sibling list, though the target object (uid) is left unnamed.

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?

There is no statement of when to reach for this versus set_fill_parameters, set_fill_resource, or apply_baking_preset, and no prerequisites (does the layer need to be a fill layer? must the preset already exist?). Usage is only inferable from the title.

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