creator_set_parameter

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

With no annotations, the description carries the burden of behavioral disclosure. It adds valuable context that for 1D parameters only x is used, and for 2D parameters both x and y are needed, which goes beyond the schema. However, it does not mention what happens if y is provided for 1D, or identifier requirements, though these are partly covered by schema.

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 concise and to the point, with two short sentences that front-load the main purpose and then provide necessary dimension-specific guidance. No redundant or irrelevant information is present.

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?

The tool is simple with only 4 parameters, all documented in the schema. The description covers the core operation and key behavioral nuance (1D vs 2D). Since there is no output schema and the complexity is low, the description is sufficiently complete for an agent to invoke the tool correctly.

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 schema already provides 100% coverage with descriptions for all four parameters, including 'Y value for vec2 parameters' and 'used if uuid is omitted'. The description adds minimal extra meaning beyond the schema, mainly restating the 1D/2D usage in a more explicit way. Thus, the baseline of 3 applies.

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 states 'Set a parameter value' with a specific verb and resource, and further clarifies behavior for 1D and 2D parameters. This clearly distinguishes it from sibling tools like creator_add_parameter or creator_remove_parameter, which use different verbs and operations.

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 provides guidance on how to use the tool (for 1D vs 2D params) but does not explicitly state when to use it over alternatives or when not to use it. It implies usage for setting parameter values but lacks explicit exclusions or references to sibling tools.

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