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

The description lacks behavioral details such as what the tool returns (e.g., status code, JSON), whether it requires authentication, or any side effects. With no annotations, the description should compensate, but it merely restates the name's implication.

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 a single, short sentence with no extraneous text. It is concise and to the point, though some might argue it is too brief to add significant value beyond the tool name.

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?

Despite the tool's simplicity, the description fails to explain the output or expected behavior. An agent cannot infer whether the result is a simple success indicator or detailed health metrics, which is a significant gap in contextual completeness.

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 has zero parameters, so the input schema coverage is 100%. The description does not need to add parameter information. It effectively signals a parameterless call.

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 'Server health check' clearly identifies the tool's purpose: checking the health status of the server. The verb is specific and the resource is evident, making it distinct from sibling tools which focus on content extraction or page navigation.

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?

No guidance is provided on when to use this tool versus alternatives. While there are sibling tools, the description does not clarify that this tool is for verifying server reachability or suggest scenarios where it should be preferred.

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