aion_admin_network_run

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

With no annotations, the description carries the full burden of disclosure. It mentions the admin token requirement but does not disclose potential side effects (e.g., network traffic, scanning behavior), output handling, or whether the operation is reversible. This is a security-sensitive arbitrary command execution tool, so the lack of behavioral detail is a significant 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 two concise sentences, front-loaded with the main action and followed by the key prerequisite. There is no redundant phrasing or unnecessary detail.

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?

This is an arbitrary command execution tool with no output schema, yet the description is extremely sparse. It does not explain the return format, execution behavior, timeouts, error modes, or any limitations. The presence of many similar sibling tools makes this incompleteness more problematic, as the agent cannot confidently predict the tool's full 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% with clear parameter descriptions for both 'command' and 'target'. The description adds minor context (mentions nmap/nikto) but does not substantially enhance understanding beyond the schema, so the baseline of 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 clearly states a verb ('Run') and a resource ('network intelligence command via Aion's admin panel'), and the Aion admin panel context distinguishes it from sibling tools like kali_exec. The examples (nmap, nikto) further clarify the tool's scope.

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 alternatives; the only additional information is a prerequisite (admin token). There is no comparison to siblings or indication of preferred use cases, so the agent is left without clear selection criteria.

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