Set Layer Style

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

No annotations provided; description mentions defaults but does not disclose whether it overwrites existing symbology, requires permissions, or has irreversible effects. Mutation is implied but not fully detailed.

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?

Two sentences front-load the core purpose and provide essential parameter details with no superfluous text.

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?

Lacks mention of return value or side effects (e.g., map auto-update). Does not specify layer type (vector). Could be more complete given no output schema.

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?

Schema has 0% parameter descriptions, but description adds meaning for all 5 parameters: explains style_type options, field requirement, classes default for graduated, color_ramp examples. Compensates fully.

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?

Clearly states 'Set layer symbology' and enumerates three style types. Differentiates from siblings like apply_style_qml (for QML files) and set_layer_labeling (for labels).

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?

Explains when to use each style_type and that field is required for categorized/graduated. Provides context but does not explicitly mention when not to use or alternatives like apply_style_qml.

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