get_color_ramp

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

No annotations are present, so the description carries the full burden. It clearly indicates a read-only operation and describes the return structure. However, it does not explicitly state idempotency or safety of multiple calls, though it is implied.

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 with three distinct sections: purpose, usage guidance, and Args/Returns. It is front-loaded with the core verb and resource, and every sentence contributes value.

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 read tool with an output schema, the description covers purpose, usage context, parameters, and return structure. It lacks mention of error handling (e.g., when material or node doesn't exist), but overall is fairly complete.

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?

Input schema has 0% description coverage, so the description's Args section adds essential meaning: 'material_name: Name of the material' and 'node_name: Name of the ColorRamp node'. This compensates for the missing schema descriptions, though it could include constraints like 'must exist'.

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 'Read every stop on a ColorRamp node', which is a specific verb+resource. It distinguishes from sibling tools like add_color_ramp_element and remove_color_ramp_element, which mutate stops.

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 explicitly recommends using this tool before editing to capture current indices and positions, explaining why (add/move operations reorder stops). It provides clear context but does not name alternative tools explicitly.

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