supervisor_start_addon

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

No annotations provided, so the description carries the full burden. It does not disclose prerequisites (add-on must be installed), side effects, or return value (though output schema exists). The behavior is minimalistically described.

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 very short (one sentence), which is efficient. However, it lacks structure (e.g., separate sections for usage, parameters, behavior). Every word contributes but is too terse.

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 simple tool with one parameter and sibling tools, the description is incomplete. It does not explain what 'start' does in practice, what response to expect, or error conditions. The existing output schema is not referenced.

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%, meaning the description adds no explanation for the single required parameter 'slug'. The description does not clarify what 'slug' refers to (e.g., add-on identifier).

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 'Start an installed add-on' uses a clear verb and resource, distinguishing it from sibling tools like 'stop_addon' or 'restart_addon'. However, it could be more specific about what 'start' entails (e.g., activating the add-on's services).

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 versus alternatives like 'supervisor_install_addon' or 'supervisor_restart_addon'. The context implies the add-on must already be installed, but this is not stated explicitly.

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