describe_statefulset

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

With no annotations, the description must disclose behavioral traits. It only says 'Shows details', implying a read operation, but gives no specifics about return format, required permissions, or potential impact (e.g., cost, size of output). The agent has little insight beyond the name.

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?

A single, direct sentence that is front-loaded with the key action. No extraneous words or details.

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 describe tool with no output schema, the description is adequate but not thorough. It does not explain what 'details' entails (e.g., status, spec, events) or how it compares to similar sibling descriptions. The lack of output schema makes this gap more noticeable.

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 each parameter is described in the schema. The description adds no additional meaning beyond what the schema provides, so it meets the baseline expectation but does not elevate it.

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 'Shows details of a StatefulSet.' uses a specific verb and resource, clearly distinguishing it from sibling tools like list_statefulsets (which lists) and describe_deployment (different resource). The purpose is unequivocal.

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 is provided on when to use this tool versus alternatives like describe_deployment or describe_pod. The description lacks context about when a user should choose this tool over others, nor does it mention prerequisites or exclusions.

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