exchange_get_server_health

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the cmdlet and Managed Availability health sets, but does not state whether this is a read-only operation, what data is returned, whether permissions are needed, or any side effects. This is a significant gap for a tool with zero annotation coverage.

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, compact sentence that front-loads the operation and includes a clarifying parenthetical. It is appropriately brief with no filler, though it could arguably include a bit more utility without becoming bloated.

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 tool with no annotations, no output schema, and an undocumented optional parameter, the description is too thin. It lacks details on the healthSet parameter, expected return shape, and when to prefer this over related sibling health tools, leaving an agent under-informed.

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 only 50%: the server parameter has a basic description, but healthSet has none. The tool description adds no information about what healthSet accepts or how it affects results, so it does not compensate for the undocumented parameter.

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 'Get' and resource 'server health', and adds specificity with 'Managed Availability health sets', which distinguishes it from generic health queries. However, it does not explicitly differentiate from sibling tools like exchange_get_health_report or exchange_test_service_health, so it falls short of a 5.

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 gives no guidance on when to use this tool versus alternatives such as exchange_get_health_report, exchange_test_service_health, or exchange_get_server_component_state. An agent has to infer the use case from the tool name and terse description.

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