aion_admin_users

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

No annotations are provided, so the description carries full responsibility. 'List' implies a read-only, non-destructive operation, and the admin session requirement is disclosed. However, it does not describe behavior when authentication fails, the response format, or any potential performance implications for large user lists.

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?

Two short sentences with no filler. The purpose is stated first, followed by a critical prerequisite. Every word earns its place, and the structure is front-loaded.

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 zero-parameter, read-only listing tool, the description covers the operation and the auth requirement adequately. It lacks details on return shape or error conditions, but the tool's simplicity and lack of output schema mean the description is nearly complete.

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 has zero parameters, making the description's job trivial. Since there are no parameters to explain, the baseline of 4 applies. The description neither adds nor omits parameter-related information.

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 uses the specific verb 'List' and identifies the resource as 'all users registered in Aion', making the tool's purpose unambiguous. It clearly distinguishes this from sibling admin tools like aion_admin_profile_rebuild or aion_admin_network_run, which concern different resources.

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 clearly states the prerequisite of an admin session (AION_SESSION_TOKEN), which is essential usage context. However, it does not explicitly mention alternatives or when not to use the tool, though no direct competing sibling exists.

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