apply_local_preset

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

With no annotations, the description carries the burden but lacks critical behavioral details. It explains intensity scaling but does not disclose mutability, whether it overwrites existing settings, or what happens when save_as is null. Insufficient for safe invocation.

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?

Concise and front-loaded with the main purpose. Lists presets and intensity scaling efficiently. The param list is slightly redundant given the schema but not wasteful. Good structure overall.

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?

Given 4 parameters and an output schema (not explained), the description is moderately complete but lacks behavioral transparency about saves and overwrites. Could be more comprehensive for a mutation tool with no annotations.

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?

Lists available presets and explains intensity scaling, adding meaning beyond the schema. However, schema coverage is 0%, and profile_path, preset, and save_as are not described besides listing them. Partially compensates, but gaps remain.

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?

Clearly states it applies a predefined local adjustment preset to a PP3 profile, specifying the resource and action. It distinguishes from siblings like 'apply_lut' or 'apply_template' by focusing on local adjustments and listing specific presets.

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?

Implies usage for local adjustment presets but does not explicitly state when to use this tool versus alternatives like 'apply_template' for global adjustments. No when-not or alternative guidance is provided.

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