statefulset_get

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The '[READ]' prefix hints at non-destructive behavior, but the description does not disclose potential error conditions, idempotency, or any side effects. Minimum viable transparency for a simple getter.

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 extremely concise, with a clear one-line summary followed by a structured parameter list. Every sentence adds value, and the most important information is front-loaded.

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?

Given the tool has three parameters, no output schema, and no annotations, the description covers the required inputs adequately. It provides a read hint and cross-reference for finding correct names. Minor gap: no explanation of what 'detail' entails in the output, but acceptable for a simple getter.

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?

Input schema coverage is 0%, so the description must explain parameters. It describes 'name' (referencing statefulset_list), 'namespace' (with guidance to omit for default), and 'target' (k8s target). This adds moderate value beyond the schema types and defaults.

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 it returns detail for a single statefulset by name, with a '[READ]' prefix indicating a read-only operation. It distinguishes from sibling tools like statefulset_list (which lists) and other get tools by explicitly naming the resource type.

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 description indicates to use statefulset_list to obtain names for the 'name' parameter, providing guidance on how to find valid inputs. However, it does not explicitly state when not to use this tool or list alternatives beyond the implicit reference.

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