restart_channel

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

With no annotations provided, the description must fully disclose behavioral traits. It reveals the operation is a stop followed by a start, implying state mutation, but lacks details on side effects, permissions, or safety (e.g., channel downtime). The brief 'stop + start' is insufficient for an agent to assess risks.

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 concise with two sentences, front-loading the core action and use case. Every sentence adds value, but the structure could be improved by separating parameter guidance or listing steps, making it slightly less than perfectly structured.

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 existence of sibling start/stop tools, the description adequately clarifies when to use restart. However, with no output schema and only one parameter hint, it lacks details on return values, error states, or additional behavioral context, making it minimally complete for a mutation tool.

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%, so the description must compensate. It adds meaning to appUuid ('must be the app UUID') but provides no context for channelId. With two parameters, this partial coverage leaves half the schema unexplained, failing to fully guide invocation.

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 'Restart a channel (stop + start)' using a specific verb and resource. It distinguishes itself from siblings like start_channel and stop_channel by explicitly combining them, and adds context 'Best for error recovery' that clarifies its unique purpose.

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?

The description provides clear usage context with 'Best for error recovery', indicating when to use restart. It also specifies 'appUuid must be the app UUID', guiding correct parameter use. However, it does not explicitly exclude other scenarios or mention alternatives like using start or stop individually.

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