Reset config to empty defaults

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

Annotations already declare readOnlyHint=false and no open-world access, so the description's "MUTATING" restates structured data; however "Immediately applies" adds real value about the lack of a pending/confirm phase. There is an unresolved tension with destructiveHint=false when the text says the existing config is cleared to empty defaults, and no statement about reversibility or whether prior settings are recoverable.

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?

Three short clauses, front-loaded with the action and ending with the two highest-value behavioral facts (immediate application, mutation). No filler.

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?

For a zero-parameter operation with full annotation coverage and no output schema, the description covers action, target, immediacy and the source method. The only real gap is scope and recoverability — which config it resets (device vs project) and whether the cleared settings can be restored.

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 tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly avoids inventing parameters.

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?

States a specific verb and resource ("Clear the firmware config to empty defaults") and names the underlying store method resetFirmwareConfig, so the agent knows exactly what happens. It doesn't explicitly contrast itself with the nearby firmware_config_set / firmware_config_edit / firmware_config_load_template siblings, but the destructive-reset semantics are distinguishable.

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?

"Immediately applies. MUTATING." signals the operation is applied without a confirmation step, which implicitly tells the agent to be careful, but there is no explicit when-to-use/when-not guidance and no mention of the alternative config tools. The agent must infer that this is the nuclear option versus firmware_config_set/edit.

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