list_iam_users

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

With no annotations, the description discloses the required auth scope (iam:users:read) and explains parameters, but does not mention other behaviors such as pagination, sorting, or return format.

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 two sentences, front-loaded with the purpose, and contains no unnecessary words. It efficiently conveys the core information.

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?

The description explains the tool's purpose and parameters but lacks details about the output (returned fields, structure). Since there is no output schema, more context on the return value would improve completeness.

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 repeats the parameter definitions already provided by the input schema (levelType, levelId) without adding new meaning. Schema coverage is 100%, so baseline is 3.

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 the tool lists active users at an organizational level, specifying 'IAM v1'. This distinguishes it from sibling tools like get_iam_user (single user) and list_iam_groups.

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 indicates the tool is for listing active users at an organizational level and requires a specific scope, but it does not explicitly state when to use this tool versus alternatives (e.g., get_iam_user for a single user).

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