ako_restart

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

Annotations indicate destructiveHint=true and readOnlyHint=false. Description adds context: 'deleting it (K8s recreates automatically)' and 'Brief traffic disruption possible.' Also explains preview mode when confirmed=False, which annotations do not cover.

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?

Description is well-structured with summary, usage, safety, and parameter list. Efficient and front-loaded. Could slightly tighten but overall clear.

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?

Covers purpose, usage, safety, and parameters. Output schema exists so return values not needed. Complete for a restart tool with safety confirmation.

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%, so description carries full burden. It explains both parameters: context as optional K8s context, confirmed as required for actual restart with default false giving preview. Provides complete semantic meaning beyond schema.

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 it restarts AKO pod by deleting it, with specific verb 'Restart' and resource 'AKO pod'. It distinguishes from sibling tools which are primarily read/diagnostic operations. Includes when to use: 'when AKO is stuck or after config changes'.

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?

Provides explicit usage context: 'Use when AKO is stuck or after config changes.' Also warns about brief traffic disruption. Explains safety mechanism with confirmed flag. Lacks explicit exclusions or alternatives, but sibling tools do not directly compete.

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