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

Goes well beyond the minimal annotations by disclosing the actual side effect (removing grain, halation, vignette, chromatic aberration, soft edges from prompts), the precondition that it only takes effect while a LensLab lens set is chosen, and the stored-but-inert case when none is set. This is exactly the mutation context an agent needs.

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?

Purpose is front-loaded and every sentence carries a distinct fact (when to use, read/write, effect, precondition, return). Some sentences are long and dash-heavy, costing a little readability, but there is no 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?

Despite no output schema, the description fully specifies the return payload (look_in_post, optik, wirkt, and a pass-along sentence), so an agent knows what comes back. Combined with the precondition detail, nothing needed to call this correctly is missing.

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 coverage is 100% so the mechanical meaning of both params is already documented, but the description enriches them by enumerating the affected prompt terms and the rendering precondition tied to the flag value. That is added meaning beyond the schema, though it does not define syntax or defaults.

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 pair ('read or set') and resource ('a project's look in post flag'), immediately distinguishing it from the many generate/grade siblings. It does not name any sibling it is not, but the flag-specific scope is unmistakable.

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?

Gives a concrete when-to-use condition: the person grades in DaVinci Resolve with the FilmLab Look plugin and wants the look applied there instead of baked in. It also specifies read vs write via omitted vs present look_in_post. No explicit exclusions or named alternatives, hence not a 5.

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