k8s_rollout_restart

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

States that all pods will be recreated in a rolling fashion, which reveals the destructive nature. However, no mention of permissions, impact on existing operations, or that it's a write operation. With no annotations, this is adequate but minimal.

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 concise sentences, front-loaded with the action and resource types. No unnecessary words.

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?

With no parameter descriptions, no output schema, and no annotations, the description fails to provide sufficient context for a tool with four required params. The agent would need to guess resource_type values and other details.

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%, and the description adds no explanation for any of the four required parameters. The agent gets no help understanding what 'context', 'name', 'namespace', or 'resource_type' mean or what valid values are.

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?

Clearly states it triggers a rolling restart for deployments, daemonsets, or statefulsets. However, it does not explicitly differentiate from sibling rollout tools like rollout_undo or rollout_resume, but the action is distinct enough.

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 guidance on when to use this tool versus alternatives, no prerequisites or conditions mentioned. Agent must infer from tool name and description.

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