Gsettings Reset

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

No annotations are supplied, so the description carries the full behavioral burden. It implies mutation but never states that the prior value is overwritten and unrecoverable, whether system-wide or per-user defaults are restored, or what happens if the key is invalid — significant gaps for a state-changing tool.

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 no wasted words. Its brevity is efficient rather than padded, though the same terseness leaves the behavioral gaps above unaddressed.

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. However, for a mutation tool with no annotations and 0% parameter documentation, the definition is thinner than the complexity warrants — the semantics of the schema/key pair and the consequences of resetting are missing.

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% and there are two required parameters (schema and key), so the description would need to compensate. It references the key only implicitly via 'a gsettings key' and says nothing about the 'schema' parameter, its format, or how schema and key pair together.

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 a specific verb (reset) and resource (a gsettings key) plus the resulting state (its default), so the operation itself is unambiguous. It does not differentiate from the sibling gsettings_set, which could achieve a similar effect by writing the default value, leaving the agent to infer the distinction.

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 guidance on when to prefer this over gsettings_set with a default value, no mention of preconditions such as the schema being installed or the key existing, and no stated behavior for non-existent keys. Usage is only implied by the word 'reset'.

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