supervisor_get_addon_stats

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

No annotations are provided, so the description must disclose behavioral traits. It only states what the tool does ('get runtime resource stats'), implying read-only but not addressing permissions, rate limits, or side effects. The term 'get' suggests non-destructive behavior, but explicit context is missing.

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?

A single sentence that efficiently conveys the purpose, listing key stat types in parentheses. No unnecessary words; it is front-loaded and easy to parse.

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 read tool with one parameter and an output schema, the description covers the core purpose but lacks parameter semantics and usage differentiation. It does not explain how to find the slug or when to prefer this over other supervisor get tools. Adequate but not fully comprehensive.

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 input schema has one parameter 'slug' with no description (0% coverage). The description does not explain what 'slug' is or how to obtain it. While the phrase 'for an add-on' implies the slug identifies an add-on, the agent needs more context to correctly construct the parameter.

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 clearly states the action ('Get'), the specific resource ('runtime resource stats (CPU, memory, network, IO)'), and the target ('an add-on'). It distinguishes from sibling tools like supervisor_get_addon (general info) and supervisor_get_addon_logs (logs).

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 explicit guidance is provided on when to use this tool versus alternatives. The description does not mention when not to use it or suggest related tools. Given multiple supervisor get tools, the agent lacks decision support.

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