it_ops_open_iac_pr

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

Annotations already indicate this is non-read-only, non-idempotent, and potentially destructive, and the description does not contradict those hints. It adds useful context about the JWT/tenant/company scope and dispatcher routing, but it does not disclose the concrete side effects of opening the PR or any confirmation or reversibility behavior.

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 brief, front-loaded, and organized into an introduction plus a clear args list. It loses a point because the opening line largely restates the tool name instead of providing a functional explanation, so the concise structure is not used to maximum effect.

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 potentially destructive dispatcher action with zero schema coverage, the description omits important invocation context: what the action actually does, when it should be called relative to related it_ops tools, and what a valid `message` or `inputs` payload looks like. An output schema exists, so return values need not be described, but the action semantics and call criteria are still 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 0%, so the description carries the full burden for parameter meaning. It provides basic semantics: `message` is a free-text objective and `inputs` is an optional JSON string for structured inputs. That is a minimal but real improvement over the schema; however, it does not explain what fields the JSON should contain or how the message should be phrased.

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 says to run the `open_iac_pr` action and that it routes through a dispatcher, but it never states what opening an IaC PR actually does or produces. This mostly restates the tool name and relies on the name itself for meaning, without distinguishing it from sibling tools like `it_ops_generate_iac` or `it_ops_plan_iac`.

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 given about when to use this tool versus the many related it_ops action tools. The routing and scope context is mentioned, but there is no indication of prerequisites, sequencing relative to generation/planning tools, or when this action should be avoided.

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