it_ops_autocompany_software_engineering_loop

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

Annotations already signal that this is destructive, non-idempotent, and not read-only. The description adds useful scoping context by stating the call routes through the platform's domain-agent dispatcher under the caller's JWT, tenant, and company scope. However, it does not disclose what the loop mutates, what external side effects occur, or whether it is long-running.

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 compact and the Args block is clearly formatted. The opening sentence is largely redundant with the tool name, and only the routing sentence and arg notes add substantive value.

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 destructive, open-world domain-agent loop, an agent needs to know what the loop accomplishes, what inputs it accepts, and when to choose it over the many sibling loop tools. None of that selection or invocation context is present, so the description is incomplete despite the routing context and output schema.

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 must compensate for parameter meaning. It does clarify that `message` is the free-text objective and `inputs` is an optional JSON string, which is sufficient for a basic invocation. However, it provides no details about what structured inputs are valid or how they should be formatted.

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 'Run the it_ops domain agent action `autocompany_software_engineering_loop`', which mostly restates the tool name without explaining what the action actually does. It gives no indication of the loop's objective, output, or effect, and it does not differentiate the tool from close siblings like it_ops_software_engineering_loop.

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 only usage signal is that `message` is a 'free-text objective', implying the tool is for open-ended objectives. There is no explicit when-to-use guidance, no exclusions, and no reference to alternatives such as it_ops_autonomous_delivery_loop or software_delivery_loop.

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