restart_pod

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

Without annotations, description discloses that it is a destructive action (pod deletion), automatic recreation behavior, and dry-run capability. Lacks mention of permissions or error cases, but sufficient.

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?

Three concise sentences with front-loaded 'WRITE ACTION' label. No wasted words, directly informative.

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 input, action, default behavior, and user confirmation. No output schema, but tool's effect is adequately described. Missing error handling info, but acceptable.

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 100%, and description adds context: dryRun default behavior and confirmation requirement, enhancing understanding beyond the 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 is a WRITE ACTION that modifies cluster state by deleting a pod, leading to recreation if managed. This distinguishes it from sibling tools like get_pod_status or list_pods.

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?

Explicitly instructs to confirm with the user before calling and to use dryRun=true (default) to preview. Provides clear when-to-use guidance, though no direct comparison to siblings.

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