list_users_2

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds the scope 'all connected users' and the HTTP endpoint, but it does not explain what 'connected' means, whether the result is paginated, or whether the user list represents current connections or authorized users.

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 short, direct, and front-loaded with the main action; the 'GET /users' line adds a concrete route reference. The phrasing is slightly terse and the second line is not strictly necessary, but overall there is no clutter.

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?

Given zero parameters, robust safety annotations, and a present output schema, the tool is mostly self-sufficient. Missing context is limited to the meaning of 'connected users' and the distinction from near-identical siblings, which prevents a perfect score.

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 tool has zero parameters, so the schema carries no semantic weight and the baseline is high. The description's phrase 'all connected users' provides a minimal but sufficient semantic hint that no parameters are needed to fetch the complete set.

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 a clear action and resource ('Get list of all connected users'), so the core purpose is understandable. However, it does not distinguish itself from closely named siblings such as 'list_users' or 'list_users_account', leaving ambiguity about what 'connected' means and why this variant exists.

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 about when to use this tool instead of sibling tools like 'list_users', 'list_home_users', or 'list_users_account'. The description does not mention prerequisites, exclusions, or alternative selection criteria.

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