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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which the description's 'Checks' aligns with. The description adds the notion of 'current' status, which implies a point-in-time check rather than a blocking wait, but it does not elaborate on whether the call waits for rollout completion or returns immediately, leaving potential ambiguity given the kubectl analogy.

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?

The description is two sentences long, front-loads the core purpose in the first sentence, and uses the second sentence for a helpful analogy. Every word earns its place, with no redundant content.

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?

The tool is a simple read-only operation with complete schema coverage, clear annotations, and an output schema. The description sufficiently orients the agent, and the kubectl analogy adds relevant context. No significant gaps exist for a tool of this complexity.

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?

The input schema has 100% coverage with detailed descriptions for all four parameters, so the schema carries the full semantic burden. The description provides no additional parameter-level details, which is acceptable given the schema's completeness; baseline 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 tool's function: 'Checks the current rollout status of a Kubernetes resource.' It includes a specific verb ('checks') and resource ('rollout status'), and the kubectl analogy ('similar to running `kubectl rollout status`') precisely conveys the intended operation, distinguishing it from generic get/describe tools.

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?

The kubectl analogy gives implicit guidance on when to use the tool (when you would run `kubectl rollout status`), but it does not explicitly mention alternatives or exclusion criteria among sibling tools. No when-not-to-use guidance is provided.

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