health_check

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

Annotations already declare readOnlyHint and openWorldHint, so safety and external reach are covered. The description adds the useful scope detail that per-server connectivity status is reported, but it says nothing about failure semantics — whether unreachable servers raise an error or are reported in-band, timeouts, or how long the check takes.

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?

Two sentences, no filler, and the scope (MCP server plus Zabbix connections) is front-loaded before the return detail. Every clause earns its place and nothing is repeated from the schema or annotations.

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-argument diagnostic with an output schema and read-only/open-world annotations, the description supplies the essentials: what is checked and what is returned. It stops short of explaining how to interpret a negative result, but the output schema can carry that.

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 takes zero parameters, so per the rubric the baseline is 4. There is no parameter meaning for the description to add or omit.

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?

States a specific verb and resource: it checks the MCP server's own health plus its connections to the configured Zabbix servers, and it names the return (per-server connectivity status). No sibling tool covers this ground — every sibling is a Zabbix entity fetch or a utility — so an agent can identify this as the diagnostic tool without ambiguity.

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?

Usage is only implied: the description says what is checked ('MCP server and its connections to Zabbix servers'), which strongly suggests calling it to diagnose connectivity problems, but it never states when to call it versus alternatives like serverinfo_get or apiinfo_version, nor what to do with an unhealthy result.

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