style_set_raster_renderer

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

No annotations are provided. The description discloses that it modifies the renderer and details the parameters for each renderer type. However, it does not mention that the existing renderer is overwritten or any potential side effects, leaving some behavioral ambiguity.

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 front-loaded with the main action. It uses a clear list-like format for renderer types, though it could be slightly more structured with explicit bullets. Every sentence adds 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?

Given the complexity of three renderer types with nested parameters, the description provides sufficient detail for most use cases. It does not describe return values, but an output schema exists. It adequately covers the tool's core functionality.

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?

With 0% schema description coverage, the description adds significant value by explaining the 'renderer_type' and 'parameters' sub-fields (e.g., band, color_ramp, azimuth). It compensates for the sparse schema, though 'layer_id' is left implicit.

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 sets a raster layer's renderer, and specifies three renderer types with their distinct parameters. This differentiates it from sibling tools like style_set_single_symbol or style_set_categorized, which apply to vector layers.

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 explains the renderer types but does not explicitly state when to use this tool vs. alternative style tools (e.g., for vector layers). No guidance on prerequisites or scenarios where this tool is inappropriate.

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