list_users

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

No annotations are provided, and the description only says 'List', leaving important behavioral context undefined—such as whether admin privileges are required, whether 'all' is relative to the caller's visibility, and whether any data is modified. While the verb 'List' suggests read-only, the description does not make this explicit.

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 entire description is one compact sentence with no filler. It front-loads the verb 'List' and clearly states the target ('database users') and the additional detail ('and their roles').

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 list tool, the description covers the basic purpose, but because there is no output schema or annotation to clarify safety and return data, some context (permission requirements and response shape) is missing. Still, the tool is simple enough that this is a modest gap.

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, and the schema has no properties with 100% coverage, so there are no parameter semantics to explain. A baseline score of 4 is appropriate because no parameter documentation is needed.

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 a specific verb ('List') and resource ('database users'), and adds 'their roles' to clarify scope. This differentiates it from related sibling tools like audit_user_permissions or get_user_permissions by emphasizing full enumeration of users rather than permission analysis.

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 the tool is for retrieving a complete user list, but it never explicitly states when to choose it over related siblings or mentions any exclusions. Usage context is only inferred from the phrasing 'List all'.

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