ha_addon_options

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits such as whether setting options triggers a restart, whether validation is performed, or whether partial updates are allowed. For a mutation tool, this is insufficient.

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, consisting of a single sentence that communicates the core purpose without any superfluous words. It is front-loaded and efficient.

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 dual get/set functionality and the absence of an output schema and annotations, the description is too minimal. It does not explain what happens on get (e.g., returns current options) or specify the expected structure for the 'options' object. More completeness is needed for a tool with two different behaviors.

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 100%, with the schema already describing 'slug' as 'Add-on slug' and 'options' as 'New options to set. Omit to get current options.' The description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 'Get or set configuration options for an add-on' clearly states the verb (get/set) and the resource (configuration options for an add-on). It effectively distinguishes this tool from siblings like 'ha_addon_info' (which likely retrieves general add-on info) and 'ha_install_addon'.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives such as 'ha_addon_info' for reading info or 'ha_start_addon' for controlling add-on state. No explicit when-to-use or when-not-to-use guidance is given.

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