exchange_list_mail_users

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

With no annotations, the description carries the full burden but only implies a read-only list operation. It gives no information about pagination, result limits, response shape, required permissions, or whether all mail users are returned.

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 short but not usefully concise; it is under-specified. It has no structure or elaboration that would help an agent decide whether to invoke it.

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?

Given one undocumented parameter, no output schema, and a large group of similar sibling tools, a single restatement of the tool name is far from complete enough. Key details such as resultSize semantics, return value shape, and differentiation from other list tools are missing.

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 only parameter, resultSize, has no schema description and is not mentioned in the tool description. An agent cannot determine what resultSize means, whether it is a maxium, an offset, or something else.

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 'List mail users' essentially restates the tool name 'exchange_list_mail_users' and provides no additional meaning. It does not clarify what counts as a mail user or how this differs from sibling tools like exchange_list_mailboxes or exchange_list_mail_contacts.

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?

There is no guidance about when to prefer this tool over the many sibling list/get tools. No use conditions, exclusions, or alternatives are mentioned.

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