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 only mentions 'Server status, API connectivity,' which hints at a read-only health check but provides no details about what exactly is checked, whether it makes network requests, or what the output represents. This is insufficient for an agent to understand the tool's 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 short, but it is not a complete sentence and reads more like a label than a functional description. While brevity is good, the lack of a verb makes it less structured and less useful. It does not waste words, but it also does not use them effectively.

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 no output schema, the description is the only source of guidance. 'Server status, API connectivity' is too sparse to fully inform an agent about the tool's purpose, expected results, or when to invoke it. Even though the tool is simple, the description leaves significant ambiguity about what the agent will receive and how to interpret 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 confirms an empty object. The baseline for 0 params is 4, and there is no need for the description to elaborate on parameter meanings. The description does not add anything param-related, but none is necessary.

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 rather than a clear verb-based statement. It indicates the tool relates to server and API health but does not explicitly say what action is performed (e.g., 'checks' or 'returns'). It is somewhat distinguishable from the news-focused sibling tools, but the purpose remains vague.

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. The description does not mention any context, prerequisites, or exclusions. An agent would have no idea whether to call health_check instead of, say, top_news or trending_topics when assessing system status.

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