run_addon

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

Adds real behavior beyond the destructiveHint annotation: the call is atomic ('one bad value refuses the whole call and changes nothing') and settings persist as if a person moved the slider. The destructive path is flagged but the description doesn't spell out what exactly gets destroyed or reset.

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 paragraphs with the core capability front-loaded and the validation/confirm caveats following. No filler, though the trailing settings-persistence sentence is slightly tangential.

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 destructive, four-parameter tool with no output schema and minimal annotations, the description covers atomicity and confirm but omits what a successful call returns, how to discover valid action names, and what 'clearing or resetting' means concretely.

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 carry the load. It explains confirm (required for clearing/resetting actions) and settings (persisted), but says nothing about the required 'addon' identifier format or where valid 'action' values come from — two of four parameters remain unexplained.

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: apply settings, run an action, or both, on an addon. This clearly separates it from list_addons and describe_addon, which are read-only siblings, though it never names them explicitly.

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?

Gives one concrete usage rule ('an action that clears or resets something needs confirm=true'), which is genuinely useful. However, it never says when to call this instead of describe_addon first, or whether action names must be discovered through a sibling, leaving the main selection decision implied.

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