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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the dangerous nature is machine-readable. The description adds nothing beyond that: it doesn't say the existing fill/stroke paint is overwritten, whether the operation is reversible, or what happens to previously defined gradients referenced by def_id.

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?

One sentence, front-loaded, with no filler. But the brevity here is under-specification rather than economy — the space saved is not spent on anything the agent needs.

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 destructive 12-parameter mutation with nested geometry, no output schema, and zero schema descriptions, the definition is nowhere near sufficient. An agent cannot determine required coordinate fields per gradient type or what gets overwritten without trial and error.

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 description coverage is 0% across 12 parameters including a nested coordinates object with 10 sub-fields. The sentence only alludes to 'fill or stroke' and 'linear or radial', which the schema's own enums already convey, and says nothing about angle, stops offsets/color/opacity, units, spread, focal points, def_id, or artboard.

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 and resource ('paint fill or stroke') plus the two gradient types, which distinguishes it from set_pattern and set_filter by implication. It never names those siblings explicitly, so the differentiation is inferred rather than stated.

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 guidance on when to use this versus set_pattern or set_style, no prerequisites (selection, artboard scope), and no conditions under which it should not be used. The agent is left to infer everything from the one-line purpose.

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