set_layer_symbology

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

With no annotations, the description carries full burden. It fails to disclose key behavioral aspects: whether it overwrites existing symbology, requires specific layer types, has destructive effects, or requires project save. The single sentence is insufficient.

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 at one sentence, with no unnecessary words. However, it sacrifices valuable content for brevity, leaving out critical usage and behavioral details.

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?

Despite schema covering parameters well, the description lacks context about the tool's effect (overwrite vs append), prerequisites (project must be saved?), and any output. For a tool with many siblings, this is insufficient for confident selection.

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 descriptions cover all 5 parameters with clear labels and brief explanations (e.g., 'Absolute .aprx path.'). The tool description adds no additional meaning beyond what the schema already provides, so 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?

The description states 'Apply symbology from a .lyrx file', which clearly indicates the action and resource. However, it does not elaborate on what 'applying symbology' entails (e.g., replacing layer's symbology) nor differentiate from sibling tools like set_layer_visibility or update_legend, which also affect layer appearance.

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 offers no guidance on when to use this tool over alternatives, such as when the symbology file is available or when to use other layer-related tools. No prerequisites or context for appropriate usage are provided.

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