exchange_list_servers

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

With no annotations, the description carries the full burden of behavioral disclosure. 'List' and 'Get-ExchangeServer' signal a read-only enumeration, but the description does not state the output shape, server scope, or any prerequisites. For a zero-parameter read operation this is adequate but minimal.

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 a single, concise sentence with the action and resource front-loaded. The parenthetical cmdlet adds grounding without unnecessary verbosity.

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 command, the description is mostly complete: no input is required, and the intent is clear. It could be improved by explicitly mentioning the alternative exchange_get_server or clarifying that it returns all servers, but no critical invocation detail is 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 tool has zero parameters, and the schema already documents an empty parameter set. The description does not add parameter detail, but none is needed, so the baseline of 4 applies.

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 verb 'List' and the resource 'Exchange servers', and adds the underlying PowerShell cmdlet name for grounding. However, it does not explicitly distinguish itself from the closely related sibling exchange_get_server, which could cause mild ambiguity about list-all versus get-one behavior.

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 usage is implied: use this tool when you want to enumerate Exchange servers. There is no explicit when-not-to-use guidance, and the related alternative exchange_get_server is not mentioned, leaving the agent to infer the distinction from the tool names alone.

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