check_mcp_health

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It mentions 'Simple health check' and 'HTTP transport,' implying a read-only operation, but it doesn't state what happens on success/failure, timeouts, or any side effects. Key behavioral details are missing.

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, both concise and purposeful. The first sentence states the action and transport, the second gives usage context. No unnecessary words or repetitions.

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?

The tool is simple (one optional parameter, no output schema, no annotations), but the description omits return value or error behavior. It gives enough to understand the general purpose, but an agent might need more details about what the health check actually returns (e.g., status code, boolean). It is minimally sufficient for a simple tool.

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 input schema has 0% description coverage, so the description must compensate. The description mentions 'another MCP server' but never explicitly explains that the server_url parameter is the target URL. While the parameter name is self-explanatory, no additional semantic value is added beyond the schema.

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 tool's function with a specific verb ('check') and resource ('another MCP server'), immediately distinguishing it from sibling tools like start_session or generate_audit_report. It explicitly mentions HTTP transport, further clarifying the tool's scope.

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 a clear usage context: 'Useful for multi-agent systems that depend on other MCP servers.' This implies when to use it, though it doesn't explicitly list alternatives or exclusions. The sibling tools are sufficiently different that no confusion arises.

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