omni_automation

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

No annotations are present, and the description does not disclose behavioral traits such as how the tool routes to sub-tools, side effects, authentication needs, or limits. The payload schema implies flexibility, but the behavior is not explained.

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 very brief (a list after a colon), but it is not well-structured. It is concise but lacks sentence-level clarity and could be reorganized for better readability.

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 complexity of 15 sub-tools, the description is severely incomplete. No output schema, no explanation of payload structure per sub-tool, and no usage examples. The tool is underdescribed 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?

Schema description coverage is 100%, so baseline is 3. The description of 'payload' adds some value by stating it must match the target tool's native inputSchema, but the tool description itself adds little extra meaning beyond listing enum values.

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 lists many sub-tools and says 'Action & control,' but it does not clearly state that the tool is a dispatcher or orchestrator. While the list gives an idea of capabilities, the purpose is vague and lacks a specific verb+resource.

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 its siblings (omni_assistant, omni_research, etc.). There is no mention of contexts or exclusions.

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