style_save_qml

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

With no annotations, the description primarily covers the basic action (saving style to file) but does not mention side effects like file overwriting, required permissions, or behavior with unsaved layers. It is adequate but not 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?

The description is a single sentence that communicates the core function efficiently without redundancy. However, it is slightly too brief, missing additional detail that could be added without harming conciseness.

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?

Given the tool's simplicity (2 required params, no enums, has output schema), the description covers the main action but omits important context like handling existing files or error conditions. It is adequate for a straightforward tool but not fully complete.

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 coverage is 0%, so the description must compensate. It implies that layer_id identifies the layer and path is the file path, but does not clarify expected file extension (e.g., .qml) or other constraints. This provides only minimal semantic help.

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 saves a layer's current style (renderer, labels, opacity) to a .qml file, specifying the exact resource and output format, which distinguishes it from sibling tools like style_load_qml.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., style_load_qml) or any preconditions such as file path validity or layer state. The description lacks explicit usage context.

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