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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It only states 'LeadOracle server status' without explaining what the status output looks like, whether the call is read-only, potential errors, or latency implications. This is insufficient for an agent to know what to expect.

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 extremely brief—four words—with no unnecessary content. It is front-loaded and to the point. However, it is a fragment rather than a complete sentence, which slightly reduces clarity, but for a zero-parameter tool, this is acceptable.

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?

Given the tool's simplicity, the description is minimal but not enough. There is no output schema and no explanation of what 'status' includes (e.g., uptime, version, latency). An agent would not know what the return value means or how to interpret 'server status'. The description should at least mention the type or format of the result.

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, and the schema is empty. Per the guidelines, a baseline of 4 is appropriate since there are no parameter semantics to explain, and the description does not need to add anything for parameters.

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 phrase 'LeadOracle server status' clearly indicates the tool checks the status of the LeadOracle server. It is distinguishable from sibling tools (company_lookup, email_finder, etc.) which handle data lookups. However, it lacks an explicit verb like 'check' or 'retrieve', making it slightly less clear.

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 guidance on when to use this tool versus alternatives, or any context such as 'use to verify server health before other operations'. The intended usage is implied by the name 'health_check' and the short description, but no explicit direction is given.

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