Check 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 only states that the tool returns health status, with no mention of side effects, permissions, rate limits, or whether it is a read-only operation. The description does not add any behavioral context beyond the bare purpose.

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, concise sentence that is front-loaded with the core purpose. There is no extraneous information, and every word earns its place. It is highly efficient and easy to parse.

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 tool with no parameters and an output schema present (as indicated by context signals), the description is adequately complete. It tells the agent what the tool does, and the output schema presumably details the structure of the health status response. The only minor gap is the lack of explicit mention that this is a read-only operation, but that is a small omission given the simplicity.

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 baseline is 4. The description does not need to elaborate on parameter semantics since there are none, and the schema is fully covered (100%). No additional meaning is required.

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 a specific verb and resource: 'Return the service health status.' It is unambiguous and immediately distinguishable from the sibling tools, which all concern mortgage calculations and products. The title and description align perfectly with the tool's function.

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 implies the tool is for checking server health but does not explicitly state when to use it versus alternatives or any exclusions. Given the sibling tools are all mortgage-related, the context makes the intended use obvious, but the description offers no explicit guidance on scenarios where this tool is the right choice or when it is not.

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