exchange_get_server

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only says server details are retrieved; it does not clarify read-only nature, required permissions, output shape, or any side effects or sensitivity.

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 sentence is short and front-loaded, but it is under-specified rather than adequately concise. It essentially restates the tool name and carries no additional 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?

With no annotations, no output schema, and many closely related siblings, the description is incomplete. An agent cannot tell what details are returned, how identity should be formatted, or when this tool is the right choice among server-related getters.

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 schema has one required string 'identity' with 0% description coverage, and the description adds no explanation of what identity should be (server name, FQDN, GUID?). The tool name weakly implies a server identifier, but this is not enough for an agent to confidently construct a valid call.

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 states a clear verb ('Get') and resource ('Exchange server details'), so an agent knows the basic operation. However, 'details' is broad and does not distinguish it from closely related siblings such as exchange_get_server_health or exchange_get_server_component_state.

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 on when to use this tool versus alternatives. It does not mention exchange_list_servers for enumeration or the health/state getters, and provides no prerequisites or typical use cases.

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