users_list

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

With no annotations, the description carries the full behavioral disclosure burden. It clearly states the read-only intent ('List') and the default/override behavior of the reseller argument. However, it does not mention authorization requirements, pagination, or how results are returned, which would add useful transparency.

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 compact and front-loaded. The main behavior is stated in the first sentence, and the Args section is minimal. No wasted words or redundant explanatory filler.

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 simple one-optional-parameter list tool with an output schema, the description covers the key behavior and parameter semantics. It is mostly complete for correct invocation, though it could mention which sibling to use when listing all users is intended.

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 description adds meaning beyond the schema by explaining the reseller parameter as an optional username and relating it to the behavior: if given, users of that reseller are listed; otherwise, the current reseller is used. This compensates for the 0% schema description coverage.

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 specific action and resource: 'List users owned by the current reseller, or by reseller if given.' This clearly conveys the tool's scope and distinguishes it from broader tools like users_list_all, though it does not explicitly name any sibling alternative.

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 when to use the tool: when you need users belonging to the current reseller or a specified reseller. It provides clear context through the owner scoping, but it does not explicitly state when not to use it or mention alternative tools such as users_search or users_list_all.

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