update_effect_style

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

Discloses that effects 'replaces the whole list' and that shadows need color+offset and blurs need radius. Annotations indicate non-destructive update, and description adds specific behavioral constraints beyond annotations.

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?

Three concise sentences: first states action, second explains partial update and effects replacement, third gives type-specific details. Front-loaded key info, no unnecessary 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?

Covers action, parameter behavior, and return format. No output schema but description provides return object. Sufficient given tool complexity.

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?

Adds meaning beyond schema: states optionality for partial updates, explains effects replacement behavior, and specifies required subfields for shadow/blur types. Schema coverage is 50%, and description compensates well.

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 clearly states 'Update an existing effect style by id' and details what can be updated (name, effects, description) with partial update semantics. Distinguishes from create_effect_style and other style update tools.

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 says 'Use this to keep a shared style in sync with code instead of creating a duplicate', providing clear usage context. Could be improved by explicitly stating when not to use, but adequate given sibling tools.

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