kubectl_rollout

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

Annotations already indicate destructiveHint: true. Description adds only 'Manage the rollout', which is generic. Does not specify that subcommands like pause, resume, undo change state, or that status is read-only.

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?

Single sentence, 15 words, avoids fluff but is too brief to be fully informative. Could include key subcommands for context without significant length increase.

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 9 parameters, no output schema, and a destructive annotation, the description lacks completeness. It fails to explain the range of subcommands (history, pause, restart, resume, status, undo) or usage patterns, leaving agents underinformed.

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% (all 9 parameters described). Description adds no additional parameter meaning beyond listing resource types, which are already in schema enums. Baseline 3 retained.

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?

Description clearly states verb (Manage) and resource (rollout of a resource) with examples. It distinguishes from siblings like kubectl_get or kubectl_describe, but could be more specific about the subcommand nature.

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 vs siblings like kubectl_apply (for initial creation) or kubectl_scale (for scaling). No when-not or alternative mentions.

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