omni_testing

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

No annotations are provided, so the description carries full burden. It does not disclose any behavioral traits such as authentication needs, rate limits, destructive potential, or output behavior. The description only lists testing types without mentioning side effects or prerequisites.

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 sentence listing domains, which is concise but lacks structure. It front-loads 'QA & Security:' but then becomes a comma-separated list. It could be better organized with bullet points or clearer grammar.

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 tool with multiple sub-tools and a nested payload parameter, the description is insufficient. It does not explain how to construct the payload, what each sub-tool does, or any expected output. The absence of an output schema further reduces completeness. Given the complexity, more context is needed.

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 input schema already describes both parameters (tool_target and payload) clearly with 100% coverage. The description adds no additional meaning beyond the schema, which is adequate but not enhanced. Baseline 3 is appropriate.

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 a broad range of testing categories (mobile, web, API, etc.) but lacks a specific verb and resource. It states it's for 'QA & Security' testing, which distinguishes it from sibling tools like omni_research or omni_automation, but the purpose is vague as it does not explain what action the tool performs (e.g., execute tests, scan, etc.).

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 description implies this tool is used for testing and security tasks, and sibling names (omni_assistant, omni_automation, etc.) provide some context. However, there is no explicit guidance on when to use this tool versus alternatives, nor any exclusions or conditions for sub-tools.

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