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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds useful context by disclosing the returned fields, including the dynamic heartbeat status dimension. It does not state whether results are paginated, how fresh the heartbeat data is, or how "pending" agents behave, so it adds moderate rather than rich value.

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?

A single front-loaded sentence with no filler, and the resource being listed is stated before the field enumeration. The dense comma list is efficient rather than padded, though it reads more as a return-field catalogue than as actionable guidance.

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 read-only, single-optional-parameter listing tool with full schema coverage and annotations covering safety, this is nearly sufficient: the description substitutes for the absent output schema by naming the fields returned. The missing piece is routing guidance among the many status/monitor siblings, which an agent still has to infer.

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 100% and the single status parameter has a documented enum, so the schema carries the parameter semantics. The description repeats the status values (up, down, pending) but adds no filtering syntax, multi-value behavior, or default-when-omitted guidance beyond what the schema states. Baseline 3 is appropriate.

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 pairs a specific verb ("Lists") with a well-defined resource ("connected physical/virtual server agents") and enumerates exactly what each entry contains (hostnames, OS types, public/private IPs, heartbeat status). An agent can distinguish this inventory-style read from metric or monitor-configuration siblings. It stops short of naming how it differs from close siblings like read_monitor_status or list_monitors.

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 when-to-use, when-not-to-use, or alternative-routing language. The agent must infer from the field list that this is an inventory/health-snapshot call rather than a metrics or configuration call. With many overlapping siblings (read_monitor_status, get_server_metrics, list_monitors), this omission is a real gap.

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