save_layer_file

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that symbology is captured, but says nothing about overwrite behavior for an existing .lyrx, required permissions, or whether the saved file references absolute vs relative paths (a live parameter). For a file-writing tool this is a significant gap.

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?

A single front-loaded sentence with essentially no waste; the required action and result are clear immediately. It is tight, though arguably undersized for a 4-parameter, un-annotated file-write tool.

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 the schema fully covers parameters. However, for a mutation tool with no annotation coverage, the description omits overwrite semantics, permission requirements, and relationship to sibling save/export tools, leaving a meaningful completeness gap.

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%, so the schema already documents map_name, layer_name, output_path and relative_paths. The description adds no syntax, format, or default behavior beyond what the schema provides, making the baseline 3 appropriate.

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 single sentence states a specific verb (Save), resource (a layer with its symbology) and output artifact (.lyrx file), so the agent can tell it apart from save_project or export_features. It stops short of naming any sibling explicitly, but the layer+symbology+lyrx framing is 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?

There is no when-to-use guidance, no mention of alternatives such as export_features or set_layer_renderer, and no prerequisites. 'For reuse' gestures at intent but does not help the agent decide whether this is the right tool for a given request.

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