create_stack

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

No annotations are included, so the description must carry the full burden. It only states 'creates a new stack' without disclosing behavioral traits like whether it overwrites existing stacks, required permissions, or error handling. For a write operation, this is insufficient.

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 with no unnecessary words. However, it could be improved by structuring key information upfront, such as required parameters or high-level behavior.

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 9 parameters and no output schema or annotations, the description is very incomplete. It fails to explain return values, side effects, or how parameters like environment and tags affect the stack creation. The schema alone does not provide sufficient context.

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 input schema has 100% description coverage for all 9 parameters, so the baseline is 3. The description does not add any additional meaning beyond the schema, nor does it explain parameter interactions or constraints.

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 creates a new stack in Komodo, using a specific verb and resource. However, it does not differentiate from sibling tools like deploy_stack or create_deployment, which could have overlapping purposes.

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?

No guidance is provided on when to use this tool versus alternatives, such as deploy_stack or create_deployment. The description lacks any conditions, prerequisites, or when-not-to-use instructions.

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