create_installation_manifests

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

With no annotations, the description carries full responsibility for disclosing side effects. It mentions creating manifests but does not state that files will be written to the install directory, whether the openshift-install binary modifies anything, or any permissions needed. The 'Returns' line is vague and adds no 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 concise and front-loaded with the main purpose. The Args and Returns sections are clearly structured. However, the Returns line ('Manifest creation results') is somewhat vague and could be more informative without adding length. Overall, it earns its place.

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?

The tool is simple with 2 parameters and an output schema, so the description covers the essentials. However, it lacks context about prerequisites (e.g., install-config must exist, openshift-install binary must be available), where manifests are written, and how this step fits into the larger installation workflow. This is adequate but not 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?

The schema has no descriptions (0% coverage), but the description's Args section adds meaningful semantics: install_dir is 'Installation directory containing install-config.yaml' and installer_path is 'Path to openshift-install binary (default: 'openshift-install')'. This goes beyond simple parameter naming and clarifies the role of each parameter.

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 'Create Kubernetes manifests from install-config.yaml' with a specific verb ('Create') and resource ('Kubernetes manifests from install-config.yaml'). This distinguishes it from sibling tools like generate_install_config and validate_install_config, which target different artifacts.

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 usage is implied: it is used when you have an install-config.yaml and want to generate manifests. However, there is no explicit guidance on when to use this tool versus alternatives like prepare_cluster_installation, nor any exclusions or prerequisites beyond the parameter descriptions.

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