get_layer_symbology

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

With no annotations, the description carries the full behavioral burden. 'Inspect ... current' reasonably signals a non-mutating read, but there is no statement about permissions, behavior when the layer is missing or the map is not active, or whether it touches the layer's state. The enumeration of returned fields also overlaps the existing output schema.

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?

One sentence, front-loaded with the verb and resource, zero filler. Nothing to trim and nothing buried.

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?

An output schema exists, so return values need not be explained, and both parameters are fully documented in the schema. For a two-parameter read tool this is nearly sufficient; the only real gap is routing guidance against the many overlapping sibling inspection tools.

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 description coverage is 100% – both layer_name and map_name are documented in the schema, including the default-active-map behavior. The description adds no additional meaning about parameter format or the layer_name vs dataset-path distinction, so the baseline 3 applies.

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?

Specific verb ('Inspect') plus a concrete resource enumeration (renderer, class breaks, unique values, label settings) makes the tool's scope unmistakable. It is implicitly the read-side counterpart to set_layer_renderer and set_layer_labeling, but it never names a sibling to differentiate itself from, e.g., get_layer_info or get_unique_values.

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 word 'current' implies the intended workflow (read existing symbology before changing it with set_layer_renderer / set_layer_labeling), but this is never stated. No when-to-use condition, no exclusions, and no pointer to the overlapping siblings get_unique_values or get_layer_info.

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