openai_list_users

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

The description adds useful context about pagination via the 'after' parameter ('Pagination cursor from a previous response's last_id'), which goes beyond the schema. However, with no annotations, it does not disclose whether the operation is read-only, permission requirements, or rate limits. The 'list' verb implies read-only but is not 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 description is concise and front-loaded with the purpose statement, followed by a structured Args list. No wasted words; every sentence provides 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?

For a simple list tool with an output schema, the description covers all parameters and the core purpose. It does not explain default behavior (e.g., default limit, ordering) or when to use it, but those are less critical given the existence of an output schema and simple operation.

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?

Schema description coverage is 0%, so the description must compensate. It clearly explains all three parameters: emails (filter), after (pagination cursor), and limit (max per page). This adds meaningful semantics beyond the raw schema types and defaults.

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 'List members of the OpenAI organization', which is a specific verb+resource. It distinguishes from siblings like openai_list_project_users (project members) and openai_get_user (single user) by explicitly scoping to organization members.

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 on when to use this tool versus alternatives is provided. It does not mention that this lists all org users, nor does it distinguish from list_project_users or get_user. The description simply states what it does without usage context.

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