Set Setting

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

The annotations already indicate destructiveHint: true. The description adds 'incorrect settings can affect QGIS behavior' which aligns with that, but does not disclose additional behavioral traits such as persistence, scope (global vs project), or whether changes require a restart. It adds minimal value beyond the annotation.

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 with two short sentences. There is no wasted verbiage. However, the brevity sacrifices important details, so it is not perfect.

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 absence of an output schema, low parameter coverage, and the tool's potentially impactful nature, the description is far from complete. It does not explain return values, common settings, or error conditions. The agent is left with insufficient information to use the tool confidently.

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 0%, so the description must compensate by explaining parameter meaning. The description does not mention 'key' or 'value' at all, leaving the agent without guidance on valid keys or value formats. This is a critical gap for effective tool usage.

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 'Write a QGIS setting' clearly indicating the verb and resource. The title 'Set Setting' reinforces the purpose. It is specific enough to understand what the tool does, but does not explicitly distinguish from sibling 'get_setting', which is implicit from the name.

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 includes a warning 'Use with care — incorrect settings can affect QGIS behavior', but does not provide explicit guidance on when to use this tool versus alternatives like 'get_setting'. It lacks context such as prerequisites or typical use cases.

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