Set Stroke

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

Annotations provide idempotentHint=true and openWorldHint=true, but description does not add significant behavioral context beyond the per-side weight capability. It does not clarify side effects like overwriting existing stroke or default behavior for missing parameters.

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?

Single sentence of 13 words, conveys purpose and key feature (uniform/per-side) with no filler. Highly efficient.

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?

Description covers main purpose but omits details about how nodeId and nodeName relate (both required, but redundancy not explained), default alpha value, and whether stroke is added or replaced. Has output schema but not leveraged.

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 coverage is 100%, but description adds meaning by explaining that uniform weight is used when individual side weights are not provided. This clarifies the relationship between 'weight' and per-side weight parameters, which is not obvious from schema alone.

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?

Description clearly states 'Set a node's stroke color and weight' with specific verb and resource. It distinguishes from siblings like node_set_fill and node_set_effects by focusing on stroke, and adds nuance with 'supports uniform or per-side weights'.

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?

The description does not explicitly state when to use this tool versus alternatives such as node_apply_style or node_set_effects. Usage context is implied by the tool name and resource, but no when-not or alternative guidance is provided.

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