restart-pod

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

Annotations indicate mutation (readOnlyHint=false) and open world. Description adds that it's a single PodAction call and mentions API version behavior (501 on v1). Does not elaborate on side effects or downtime, but sufficient given annotations.

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?

Two sentences, front-loaded with key information, no redundancy. Every sentence adds value (action, v2 constraint, v1 workaround).

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?

For a simple tool with one parameter and no output schema, the description covers action, API version, and parameter ID. Could mention state prerequisites (e.g., pod must be running) or behavior if not running, but adequate overall.

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% for the single parameter podId, and its description in schema is clear. The tool description does not add extra semantics beyond the schema, so baseline score of 3 applies.

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 (restart) and resource (pod), and implies a single call. It distinguishes from the v1 stop+start approach, but does not explicitly contrast with sibling tools like start-pod or stop-pod.

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 version-specific guidance: v2-only, and instructs to use stop+start on v1. However, lacks explicit when-to-use vs start/stop, and does not state prerequisites like pod must be running (though implied).

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