Sets a sketch's random seed to make generative output reproducible, or generates a random seed when none is supplied.
Set the random seed of a sketch, optionally generating a random value
| Name | Required | Description | Default |
|---|---|---|---|
| seed | No | Explicit seed value (default: generate random 0–99999) | |
| sketchId | Yes | ID of the sketch to update |
Changes observed during successful MCP inspections.
v0.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It states the basic action and optional random generation, but does not explain side effects such as whether the existing seed is overwritten, how determinism is affected, or whether the change is reversible.
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 with no filler. The core action is front-loaded, and the optional behavior is stated compactly.
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 simple two-parameter tool with full schema coverage, the description covers the invocation basics. However, with no annotations or output schema, it omits behavioral context about deterministic state and mutation effects that an agent might want before calling it.
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 100%, so the schema already documents both parameters, including the seed default and sketchId. The description adds only marginal semantic value by confirming that the seed can be generated randomly.
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 a specific verb and resource: setting the random seed of a sketch. It also mentions optional random value generation. It does not explicitly distinguish this from nearby tools such as randomize_parameters, so it falls short of a 5.
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 phrase 'optionally generating a random value' implies that omitting a seed creates a random one, but there is no explicit guidance on when to use this tool versus randomize_parameters or set_parameters. Usage is implied rather than clearly specified.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.