list_deployment_configs

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

No annotations are provided, so the description carries full responsibility. It does disclose the default behavior for `namespace` and `cluster` (empty = all/default) and the output columns introduced. However, it does not mention pagination, permissions, error conditions, or whether this is a read-only operation beyond the implicit 'List' verb.

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 compact and front-loaded with the core purpose. Each sentence earns its place, and the parameter details are clearly separated. There is no fluff or repetition.

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 two-parameter list operation with an output schema available, the description covers the resource type, output columns, and parameter semantics. It lacks only explicit differentiation from the close sibling `list_deployments` and any mention of operational constraints like permissions, but overall it is adequately complete.

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 must fully explain the parameters. It does: `namespace` is described as 'Namespace to query (empty = all namespaces)' and `cluster` as 'Named cluster to target (empty = default)'. This adds real meaning beyond the bare schema 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 states a specific verb ('List'), a specific resource ('OpenShift DeploymentConfigs'), and the exact API group ('apps.openshift.io/v1'), plus the columns returned. This makes the tool's purpose unambiguous and distinguishes it from the related sibling `list_deployments` which targets Kubernetes Deployments.

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 explains parameter behavior but gives no guidance on when to use this tool versus alternatives such as `list_deployments` or `rollout_deployment_config`. There is no mention of exclusions, prerequisites, or preferred use cases.

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