set_color_ramp_element

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

With no annotations, the description effectively discloses key behavioral traits: indices may shift after the call, and the need to read back for certainty. It also specifies that operation is a modification (move/recolor) and includes parameter ranges (position 0-1). This goes beyond basic schema information.

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 highly concise: a one-line summary, a brief behavioral note, structured Args list, and a Returns line. Every sentence adds value with no redundancy or fluff.

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 tool's complexity (5 params, mutation, index shifting) and the presence of an output schema (not shown but mentioned), the description adequately explains input, behavior, and return value. Minor omissions (e.g., error conditions for invalid index) prevent a perfect score.

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 description fully documents all 5 parameters in the Args section, including meaning, format, and default behavior (omit to leave unchanged). This is critical given 0% schema description coverage, and the description covers 100% of parameters effectively.

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 moves or recolors an existing ColorRamp stop, distinguishing it from siblings like add/remove/read color ramp tools. The verb-resource combination is specific and unambiguous.

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 usage constraints (at least one of position or color must be given) and advises reading back the ramp after use for certainty, but does not explicitly compare to alternative tools for similar tasks, limiting guidance on when to use this tool over others.

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