omni_systems

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

No annotations provided; description fails to disclose behavioral traits such as side effects, required permissions, or error behavior. The tool dispatches to various infrastructure actions, but the description does not indicate what happens upon invocation.

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?

Description is brief but unstructured—a single line listing many items. It is not front-loaded with a clear purpose, and the list format reduces readability. While concise, it sacrifices clarity.

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?

With no output schema and no annotations, the description is severely incomplete for a complex routing tool. It lacks return value details, error handling, and guidance on constructing the payload for each sub-tool.

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?

Input schema covers 100% of parameters with descriptions (tool_target enum and payload object). However, the description adds no meaning beyond the schema; it does not explain the sub-tools or payload structure further. Baseline 3 per guidelines.

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?

Description lists sub-tools like 'database, health check, analytics' but lacks a unified verb and resource. It does not distinguish its purpose from sibling tools; it reads as a catch-all infrastructure router.

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 explicit guidance on when to use omni_systems versus siblings (omni_assistant, omni_automation, etc.). The description provides no context for appropriate usage or exclusions.

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