replicaset_list

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

The readOnlyHint annotation already declares the safe read profile, and the "[READ]" tag merely restates it. The description usefully discloses the return columns, but says nothing about pagination, result limits, or performance on large clusters.

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?

Front-loaded with the verb and resource, followed by return fields, then a compact Args block. No filler, though the "[READ]" prefix is redundant with the annotation.

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 two-parameter read-only list with no output schema, the definition is nearly complete: it covers scoping behavior, the target selector, and the shape of returned rows. Only pagination/limit behavior is unaddressed.

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%, so the description carries the full burden and does so capably: namespace is explained ("omit for all namespaces") and target is glossed as "k8s target name from config". This meaningfully clarifies both parameters beyond the bare null-defaulted schema.

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?

States a specific verb and resource ("List replicasets") and even enumerates the returned fields (name, namespace, desired/ready, age). It does not explicitly point to a sibling, but the resource name is distinctive enough against job_list/cronjob_list/deployment_list that confusion is unlikely.

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?

Provides one concrete usage rule ("omit namespace for all namespaces") and documents the target selector, which is helpful context. However, it gives no when-to-use framing versus the get/describe siblings and no indication of when listing is preferable.

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