omni_swarm

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

No annotations are provided, and the description gives no information about side effects, authorization needs, rate limits, or whether operations are destructive. For a meta-tool that dispatches to various sub-tools, this is a critical gap.

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 a single run-on sentence with a colon and a long list, making it hard to parse. It could be much more concise by stating it is a dispatcher and referencing the sub-tool-specific inputs.

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 does not explain that payload must match the target tool's schema, nor does it mention the need for deep knowledge of each sub-tool's inputs. No output schema is provided, and the description adds no context about return values or behavior.

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 coverage is 100%, so baseline is 3. The description adds no additional meaning beyond the schema; the list of enum values is redundant with the tool_target parameter.

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 'Agent orchestration' which conveys a general purpose, but the rest is a comma-separated list of sub-tools, essentially repeating the enum values without a clear verb or overall action. It does not distinguish itself from sibling tools like omni_assistant or omni_automation.

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 this tool versus alternatives, no prerequisites or conditions mentioned. The description does not help an agent decide between omni_swarm and its siblings.

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