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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds the set of mutable style properties but does not explain overwrite behavior, scope, or what happens to omitted properties.

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 description is a single front-loaded sentence with no wasted words. However, it is under-specified for a 9-parameter destructive mutation tool, so its brevity comes at the cost of necessary detail.

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 the tool's complexity, destructive nature, 0% schema description coverage, and lack of an output schema, the description is incomplete. It does not mention the required shape_ids target, defaults, overwrite semantics, or how the enumerated properties map to the actual parameters.

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 9 parameters, so the description must compensate but only partially does. It names fill, stroke, caps, joins, taper, and opacity, but omits the required shape_ids parameter, stroke_width, and stroke_taper_amount, and provides no formats or defaults.

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 description uses a specific verb, 'Change', and names the style attributes affected: fill, stroke, caps, joins, taper, and opacity. It clearly conveys a styling mutation but does not distinguish itself from related siblings like define_styles, set_gradient, or set_pattern.

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?

It gives no guidance on when to use this tool versus alternatives such as define_styles or set_gradient, nor does it state prerequisites or exclusions. The usage is only implied by the word 'Change'.

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