monitor_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 adds some context—real-time checking, OpenTelemetry-based metrics collection, and detailed response analysis—but does not state whether the operation is read-only, whether it requires authentication, how failures are handled, or whether it has side effects. It is adequate but incomplete for a monitoring 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 two sentences and front-loads the core operation. The second sentence adds some context but includes slightly fluffy marketing-like phrasing ('comprehensive health monitoring with detailed response analysis') that could be tightened. Nonetheless, it is efficient overall.

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?

An output schema exists and the input schema is fully documented, so the description need not explain return values or parameter details. However, for a health-check tool with no annotations, the description is missing key contextual elements: when to use it versus similar siblings, whether it is safe/read-only, and how failures are surfaced. It is minimally adequate given the structured data richness but leaves notable gaps.

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%, so the input schema already documents all three parameters thoroughly, including formats, defaults, and allowed ranges. The description adds no additional parameter meaning or usage nuance beyond what the schema provides, making the baseline 3 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?

States a specific verb and resource: 'Perform real-time health check on an MCP server or web service.' The purpose is clear and concrete. It does not explicitly differentiate itself from sibling tools like check_stack_status, which likely performs a similar health-check function, so it falls short of the 5 criteria.

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 provides no when-to-use guidance, no prerequisites, and no alternatives. It does not explain when an agent should choose monitor_server_health over check_stack_status, monitor_system_resources, or other sibling tools. Usage is only implied by the phrase 'health check.'

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