set_stroke

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

The description implies a mutation operation ('Set') but does not disclose any side effects, permission requirements, or reversibility. With no annotations, the description fails to sufficiently inform the agent about behavioral traits.

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, clear sentence that efficiently communicates the tool's purpose and capability. It avoids unnecessary details while remaining informative.

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 tool with 11 parameters and no output schema, the description provides the core functionality but lacks details on return values, error states, or behavior when parameters conflict. It is minimally adequate.

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?

All 11 parameters have schema descriptions, achieving 100% coverage. The description adds context about uniform vs. individual side weights, which aids usage, but does not significantly enhance the schema's explanations.

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 stroke color and weight for a node in Figma, with support for uniform and individual side weights. While it does not explicitly differentiate from sibling tools, the specific action and object are clear.

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 `apply_style` or `manage_style`. There is no mention of prerequisites or scenarios where it should be avoided.

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