supervisor_set_addon_options

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

With no annotations, description must disclose side effects, authorization, or whether options override. It only says 'set', lacking details on mutation behavior.

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?

Single sentence, but includes redundant formatting note that could be omitted. Too terse to be helpful; prioritizes brevity over completeness.

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?

Omits essential context like prerequisites (add-on installed), output/error behavior, and how to obtain slug. Inadequate for an agent to use correctly among many supervisor tools.

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%, yet description adds negligible value beyond property names. 'Sent as {"options": options}' is confusing and does not explain expected structure for options.

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?

Clearly states 'Set configuration options for an add-on', specifying the action and resource. Differentiates from sibling tools like supervisor_get_addon and supervisor_start_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 guidance on when to use this tool vs alternatives, e.g., installing an add-on first, or checking current options. Missing context for appropriate invocation.

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