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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the tool's safety profile is known. The description adds valuable behavioral context beyond these: 'No authentication required and not metered' and 'Returns immediately.' These details inform the agent that the tool is lightweight and has no side effects, which is useful for deciding to use it in polling scenarios. No contradictions with annotations.

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, consisting of two sentences. The core purpose is front-loaded ('Returns immediately if the API is up'), followed by two important usage constraints (no auth, not metered) and a safety note. Every sentence adds value, and there is no wasted wording. It is well-structured and easy to scan.

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 simple, parameterless health check, the description is complete. It covers the tool's purpose, the conditions under which it should be used (polling from monitoring systems), and its safety profile (no auth, not metered). The annotations already handle the read-only and idempotent aspects. No output schema is present, but for a health check, the return format is likely trivial and not necessary to describe. An agent has all the information needed to invoke it 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, and the input schema is empty. Per the rubric, a zero-parameter tool receives a baseline score of 4 because there is no need for parameter documentation. The description appropriately focuses on the tool's behavior rather than parameters, which is correct for a parameterless health check.

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 states a clear, specific purpose: 'Returns immediately if the API is up.' This identifies the tool as a health check, which is distinct from the many data-retrieval siblings. It names the resource (API) and the action (checking availability), so an agent can immediately understand what it does without confusion.

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 clear usage context: 'safe to poll from a load balancer, uptime monitor, or status dashboard without affecting your usage.' This tells the agent when it's appropriate to call the tool (for health checks and monitoring). However, it does not explicitly mention alternatives or when not to use it, such as distinguishing from ping_head, which is a sibling that likely performs a HEAD request. Still, the intended use case is well conveyed.

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