set_art_brief

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

With no annotations, the description carries the full burden, and it does disclose meaningful semantics: images are reference evidence rather than automatic extraction, and existing assets require explicit edits. However, it omits core mutation behavior for a 'persist' tool — whether an existing brief is overwritten, what authorization is needed, or the side effects on referenced assets.

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 core action is front-loaded, which is good, but the following two sentences are defensive caveats ('client's vision for interpretation', 'not a claim of automatic style extraction') that crowd out practical detail. Appropriately short but not maximally information-dense.

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 mutation tool with no annotations, no output schema, and 0% parameter coverage, the description leaves too much unstated: parameter meanings, overwrite/return behavior, and relationship to sibling style tools. It covers intent but not the operational picture an agent needs.

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 0%, so the description must define all four parameters, but it never maps them. 'Reference image' loosely gestures at image_path/reference_asset, and 'recipe style/palette' at overrides, yet 'notes', 'overrides', and the image_path vs reference_asset distinction are left entirely 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 opening clause states a clear verb and resource: 'Persist a reference image and art direction,' with the optional style/palette adoption noted. It does not distinguish this tool from adjacent siblings like set_project_style or create_style_kit, so it stops short of a 5.

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 explicit when-to-use, when-not-to-use, or named alternative. The line 'Existing assets require explicit edits' hints at a constraint but does not tell the agent which sibling to reach for instead, leaving routing to inference.

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