Health

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

With no annotations, the description carries the full burden and delivers almost nothing: no indication of whether this is a safe read, whether it hits the network, what it returns, or what a failure looks like. Only the implicit read-only nature of a "check" is conveyed.

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?

Extremely short and front-loaded, but it is a bare noun phrase rather than a sentence and omits information an agent needs. Brevity here reads as under-specification rather than discipline.

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-parameter tool with no output schema, the description should at minimum state what is checked and what the response signifies. Neither is present, leaving the agent unable to interpret the output or confirm it targets the expected system.

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 and the schema is empty with 100% coverage, so there is nothing for the description to clarify. Baseline 4 applies; a small deduction for not confirming the no-input contract in prose.

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?

"Health check endpoint" restates the tool name and title without adding a verb, a target, or a scope. It does not say what is being health-checked (the MCP server itself, a remote host, an API) or what a result signifies, so an agent cannot distinguish it from siblings like system_status or check_required_tools.

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 guidance, no exclusion criteria, and no mention of any sibling tool. The description offers no signal for choosing this over system_status or check_required_tools, which appear to overlap in intent.

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