Apply a paint style to a node's strokes to keep borders consistent with your design system. Use set_stroke_color instead for raw color, weight, align, or dash values.
Apply a paint style to a node's strokes (design-system preferred). For raw color/weight/align/dash without a style, use set_stroke_color instead.
| Name | Required | Description | Default |
|---|---|---|---|
| nodeId | Yes | ||
| styleId | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full behavioral burden. It implies mutation but does not disclose whether existing stroke properties are overwritten, what permissions or preconditions are required, or how the operation affects the node beyond applying a style.
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 short sentences with zero waste. The primary purpose is front-loaded and the routing instruction follows immediately.
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?
Adequate for a simple two-parameter tool with no output schema, but missing key behavioral context such as overwrite semantics and prerequisites. With no annotations available, the description should do more to make invocation safe and predictable.
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% for both parameters. The description links styleId to 'paint style' and nodeId to 'a node's strokes' only indirectly, but does not clarify formats, constraints, or whether the style must already exist.
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 (Apply), resource (a paint style to a node's strokes), and explicitly distinguishes itself from the sibling set_stroke_color by naming the alternative and the condition that selects it.
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 to use set_stroke_color instead when applying raw color/weight/align/dash without a style, and notes design-system preference. The when-to-use and alternative path are fully stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.