Set Setting

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

The description includes a warning that incorrect settings can affect QGIS behavior, which aligns with the 'destructiveHint' annotation. However, it adds minimal context beyond the annotation, lacking specifics on potential consequences (e.g., crashes, requiring restart). No contradiction found.

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 very concise with a single direct sentence and a warning. It is appropriately front-loaded, but could benefit from slightly more detail without losing brevity.

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 lack of parameter descriptions and no output schema, the description is incomplete. It fails to convey necessary operational details like valid key-value pairs or what the tool does beyond a generic 'write'.

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?

The description provides no information about the parameters 'key' and 'value'. With 0% schema description coverage, the gaps are significant—no guidance on valid keys, value formats, or examples.

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 verb 'Write' and the resource 'QGIS setting', establishing a clear purpose. However, it lacks specificity about the scope of settings (e.g., global vs. project) and does not differentiate from related tools like 'get_setting' or 'set_project_variable'.

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 explicit guidance on when to use this tool versus alternatives. The warning 'Use with care' implies caution but does not provide context for appropriate usage or exclusion criteria.

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