oc_install_operator

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

With no annotations provided, the description carries the full burden. It states that it installs an operator but does not disclose side effects like namespace creation, CRD installation, or OLM subscription behavior. The schema hints at createNamespace and installPlanApproval, but the description itself lacks behavioral detail.

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 a single, concise sentence that front-loads the key information: install, operator, cluster, and methods. Every word earns its place with no redundancy.

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 complex tool with 10 parameters and multiple installation methods, the description is minimal. It provides a high-level overview but lacks guidance on how to select the source method or what happens after installation. The schema provides detailed parameter descriptions, but the overall context is incomplete.

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 100%, so the schema fully documents each parameter. The description adds no additional parameter context or examples, providing no value beyond the schema. Baseline 3 is appropriate.

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 verb 'Install' and the resource 'an Operator' on an OpenShift/Kubernetes cluster, specifying three installation methods. This distinguishes it from sibling tools like oc_create or oc_apply, which handle general resource creation, while this is specific to operator installation.

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 implies usage context by mentioning OLM, Helm, or direct manifests, but does not explicitly state when to choose this tool over alternatives or when to use each source method. It gives no exclusions or prerequisites, leaving the agent to infer from the schema.

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