list_users

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic action and filtering ability, but does not mention important behaviors such as pagination (though parameters first/max exist), rate limits, authentication requirements, or whether it is a read-only operation. The minimal description fails to inform the agent about side effects or constraints.

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 very concise, consisting of a single sentence that covers the core purpose. It is front-loaded with the action and scope. However, it could be slightly more informative without becoming verbose, e.g., by noting the output or pagination.

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?

With 15 parameters and no output schema, the description lacks sufficient detail for an agent to fully understand the tool's capabilities and limitations. It does not explain how multiple filters combine, the expected output structure, or any ordering/sorting. The description is inadequate for the complexity of the tool.

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 100% documentation coverage for all 15 parameters, so the description does not need to add much detail. However, the description itself adds no extra meaning beyond 'optional filtering', and does not explain how parameters interact or any special constraints. Given the high schema coverage, a 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 that the tool lists users in a realm with optional filtering, which distinguishes it from siblings like count_users or get_user. However, it does not explicitly state that it returns a list of user objects, leaving some ambiguity about the output format.

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 such as count_users, get_user, or list_user_sessions. The description does not mention any use cases, prerequisites, or exclusions, leaving the agent to infer usage from the tool name alone.

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