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

With no annotations, the description carries the full burden of behavioral disclosure. It gives no details about what the tool returns, whether it is a simple ping, or any side effects. 'Server status, API connectivity' is an under-specified subject matter rather than a disclosure of behavior.

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 fragment without a subject-verb structure. It is not concise in a purposeful way; it is under-specified. It lacks a clear sentence and does not provide structured information about the tool.

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?

Even for a simple tool with no parameters or output schema, the description is incomplete. It leaves out what result to expect and how to interpret the status. The bare phrase 'Server status, API connectivity' does not sufficiently prepare an agent to invoke the tool correctly.

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 schema coverage is 100% and the description does not need to explain parameter semantics. Baseline 4 applies because there is nothing to compensate for.

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 status, API connectivity' is a noun phrase that vaguely indicates the tool reports on server/API health, but lacks a clear verb and does not explicitly state an action such as 'checks' or 'returns'. It does differentiate from sibling data retrieval tools by its health-check focus, but without a verb the purpose is ambiguous.

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 alternatives. It does not mention any prerequisites, exclusions, or typical scenarios such as verifying connectivity before making data queries, leaving the agent without direction.

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