supervisor_get_addon_logs

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

No annotations are provided, so the description carries the full burden. It discloses the return format but lacks side effect information, auth requirements, or limitations (e.g., max lines, add-on must be running). As a read operation, 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?

A single, clear sentence that conveys the core functionality efficiently. It is concise without being verbose, though it could benefit from including the parameter explanation.

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 tool's two parameters, lack of parameter descriptions in schema, and no annotations, the description is insufficient for an agent to understand how to use the tool correctly. The output schema is not shown, but the description hints at the return format, which is good but not enough.

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 0% description coverage for its parameters. The description does not explain what 'slug' or 'lines' mean, despite 'lines' being only implicitly mentioned as 'N'. This leaves the agent without clear parameter semantics.

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 last N log lines'), the resource ('add-on'), and even mentions the return format ('{logs: ...}'). It distinguishes itself from sibling tools like supervisor_get_addon and supervisor_get_addon_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 usage guidelines are provided. The description does not indicate when to use this tool over other related tools, nor does it mention any conditions or prerequisites for using it.

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