Set Layer Style

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the basic function without mentioning side effects (e.g., permanent modification to layer), prerequisites (layer must exist and support symbology), permission requirements, or error conditions. This is insufficient for a mutation tool.

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 extremely concise: two short sentences front-loading the purpose and then listing parameter details. Every word adds value, with no redundant or filler language.

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 tool with no output schema and no annotations, the description covers core parameter constraints but lacks guidance on error handling, layer type compatibility (vector vs raster), or relationship to other style tools (e.g., apply_style_qml). It is adequate for simple use but incomplete for complex scenarios.

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 explains four of five parameters (style_type values, field requirement, color_ramp examples, classes default). The layer_id parameter is omitted but is a common identifier whose meaning is self-evident. Overall, description adds significant meaning beyond the schema.

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 symbology, lists three specific style types (single, categorized, graduated) which distinguishes it from sibling tools like apply_style_qml or set_layer_labeling. The verb 'set' + resource 'symbology' 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?

It provides clear context on when to use each style type and which parameters are required (field for categorized/graduated, classes for graduated). However, it does not explicitly state when not to use this tool or suggest alternatives like apply_style_qml for QML files, which would be helpful given the many sibling style-related tools.

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