list_users

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

With no annotations, the description carries the full burden. It reveals that results are limited to users visible to the current token, giving a behavioral constraint. However, it does not discuss authentication needs, rate limits, pagination behavior, or whether the operation is safe (though it is implicitly read-only).

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 extremely concise: one sentence for purpose, two sentences for parameter guidance. No filler, front-loaded, and each sentence adds value.

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?

Despite the 'select' parameter being well-explained, the description lacks details on 'limit', 'offset', 'search', return format, and any other behaviors. Given 4 parameters and no output schema, the description is insufficient for complete understanding.

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 schema coverage is 0%, so the description must compensate. It provides detailed semantics for the 'select' parameter (with examples and error behavior), but offers no explanation for 'limit', 'offset', or 'search' beyond their names. This partial coverage results in a mid-range score.

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 explicitly states 'List users visible to the current token,' which clearly identifies the verb (list), resource (users), and scope (visibility). This distinguishes it from siblings like 'get_user' (single user) and other list tools.

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 does not provide any guidance on when to use this tool versus alternatives such as 'list_principals' or 'get_user'. No when-to-use or when-not-to-use advice is given.

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