set_stroke_color

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

Without annotations, the description must disclose mutations and side effects. It only states 'set', but doesn't explain what happens if the node lacks stroke, whether existing stroke settings are overwritten, or what errors may occur (e.g., node not found).

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, efficient sentence that directly conveys the primary purpose with 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?

Given the lack of annotations and output schema, the description should provide context on return values, error handling, and behavioral details. It fails to mention result format or any constraints beyond the schema.

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?

The input schema has 100% description coverage for all 6 parameters. The tool description groups them under 'stroke color' but adds no additional semantic nuance beyond the schema descriptions.

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 clearly states the tool sets the stroke color of a node in Figma, which differentiates it from tools like set_fill_color. However, it doesn't mention that the tool also accepts a 'weight' parameter for stroke weight, leaving some ambiguity about the full scope.

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?

No guidance is provided on when to use this tool versus alternatives like set_fill_color or set_default_connector. There are no prerequisites or exclusion conditions mentioned.

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