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

Adds real context beyond annotations: the call is PROJECT-SCOPED and returns the project identity with its result, matte_weighted alters the subject in thermal/xray, stage=over_type also finishes the type, and 'short luminance flips count as flashes' warns of a flashing safety constraint. Annotations only declare non-readonly, non-destructive, non-idempotent; the description usefully extends this, though it omits permission/auth needs and mutation-reversibility.

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?

Front-loads the important PROJECT-SCOPED constraint, which is good structure. However the middle is dense jargon, and sentences like 'Variants are metaphors (mechanism, inside the body, data), never decoration' and the trailing flash note are cryptic rather than crisp, so it neither wastes fully nor earns every line.

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 15-parameter, nested-region effect tool with no output schema and only 40% param coverage, the description establishes scope and a few key behaviors but leaves many parameters and the return shape unexplained. It is adequate but leaves clear gaps an agent would need filled.

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?

With 15 params at 40% schema coverage, the description carries some of the burden: it explains matte_weighted and stage=over_type, and implies start/end range semantics. But the kind list merely restates the schema enum, and id, scale, origin, region, palette, strength, direction, ramp_in_f and ramp_out_f remain undocumented in both places, so it only partially compensates.

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?

States a specific verb+resource: it applies a 'picture finish' over a [start, end) range and enumerates the finish kinds (lcd/crt/led, halftone, film, thermal, etc.). An agent can tell it adds a named finish effect. However, it never contrasts itself with near-neighbours like add_stylize, add_custom_filter, or apply_look, so sibling differentiation is left implicit.

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 explicit when-to-use or when-not-to-use guidance appears. There is no mention of alternatives (add_stylize, apply_look) or prerequisites beyond the project-scoping note. The claim that variants are 'metaphors ... never decoration' is stylistic doctrine, not routing guidance.

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