supervisor_get_addon_stats

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

The description discloses that the tool returns CPU, memory, network, and IO stats. It does not state side effects, permissions, or whether it's read-only. With no annotations, the description carries the burden, but 'get' implies a read operation. Adding explicit safety notes would improve transparency.

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 a single sentence that efficiently conveys the purpose and scope. No redundant words or information, front-loaded with the core action.

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?

The description is adequate for a simple get-stats operation. It covers what stats are returned. However, it could be improved by noting whether stats are real-time or cumulative, and where to find the slug. The output schema exists (from context) so return format is covered externally.

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 schema has 1 parameter ('slug') with 0% description coverage. The description does not explain what 'slug' is or how to obtain it for an add-on. Since schema coverage is low, the description should compensate but fails to add meaning beyond the schema's type.

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 verb 'Get' and the resource 'runtime resource stats... for an add-on', listing specific stat types (CPU, memory, network, IO). It distinguishes from siblings like 'supervisor_get_addon' and 'supervisor_get_addon_logs' by focusing on stats.

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 on when to use this tool vs alternatives. The usage is implied for retrieving stats, but no conditions or exclusions are mentioned. Sibling tools suggest other add-on operations, but the description does not guide the agent on when to pick this one.

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