it_ops_aws_cli_execute

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

The description adds minimal behavioral context beyond the annotations. It mentions routing under JWT, tenant, and company scope, which relates to authorization but does not disclose potential destructive effects, side effects, or the fact that it likely executes arbitrary AWS CLI commands. The destructiveHint annotation is true, but the description offers no elaboration.

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, with a short primary statement, a brief routing explanation, and an args list. There is no fluff or redundant information. The structure is clear and easy to read.

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 description lacks essential context about what the AWS CLI action does, expected outputs, potential risks, or any examples. It does not clarify the relationship to other IT ops tools or when this generic executor should be chosen. The absence of output schema details and parameter constraints leaves the tool underspecified for effective use.

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 description provides some semantic meaning for the parameters: 'message' is described as a free-text objective and 'inputs' as an optional JSON string. However, it does not explain what constitutes a valid objective or the expected structure of the JSON, leaving significant ambiguity. Given the schema has zero description coverage, this partial explanation is better than nothing but still insufficient.

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 'Run the it_ops domain agent action `aws_cli_execute`' which essentially restates the tool name without clarifying what the AWS CLI action actually does. It does not mention AWS, CLI commands, or any specific capability, leaving the purpose vague and confusing.

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?

There is no guidance on when to use this tool versus the many sibling tools, nor any indication of appropriate use cases, prerequisites, or scenarios where it should be avoided. The description only explains the routing mechanism, not usage intent.

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