create_paint_style

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

No annotations contradict description; description adds context that tool behaves like set_fills and that slashes enable folder grouping, which is useful beyond annotations' booleans.

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?

Two sentences efficiently convey purpose, input shape, naming convention, and related tools; no wasted words.

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?

Adequately covers functionality for a tool with no output schema; mentions return value and usage pattern, though could elaborate on style being local.

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 baseline is 3; description adds minor context like 'use slashes for folder grouping' and 'same shape as set_fills', but does not significantly enhance parameter understanding beyond schema.

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?

Description uses specific verb 'create' and resource 'reusable local paint style', distinguishes from siblings like create_effect_style and create_text_style by specifying solid/gradient paints and folder grouping via slashes.

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?

Explicitly mentions when to use (creating a reusable style from solid/gradient paints) and directs to siblings apply_style_to_node and update_paint_style for subsequent actions, though does not explicitly state when not to use.

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