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 only lists the types of information returned (status, connectivity, features) and does not state side effects, authentication needs, rate limits, or whether the operation is read-only. This is a significant gap for a tool with zero annotation coverage.

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 concise at six words, which is front-loaded and free of fluff. However, it is a noun-phrase fragment rather than a proper sentence, which sacrifices clarity and structure. It reads more like a label than an explanatory description.

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 with no parameters and no output schema. The description lists the primary outputs (server status, API connectivity, supported features) which provides a baseline understanding. However, it lacks detail on the format, possible values, or how to interpret the results. It is minimally adequate but not complete.

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 explain parameter meanings because there are none to document. The schema is empty and fully covers the parameter surface.

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 is a fragment listing 'Server status, API connectivity, supported features.' It lacks an explicit verb to state what the tool does, though the subject matter implies a health-check function. It distinguishes from the flight-search sibling tools by topic, but the purpose is vague without an action verb.

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 guidance on when to use this tool versus the sibling tools. The sibling names (e.g., flight_search) suggest a flight-related API context, but the description itself does not mention when a caller should run a health check. No alternatives or exclusions are given.

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