market_coingecko_ping

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

With no annotations provided, the description must carry the behavioral disclosure burden. It clearly implies a read-only status check, but does not specify what 'status' means (e.g., HTTP code, latency, regional availability), what the return value looks like, or whether any API key or rate limits apply. It is minimally transparent but not misleading.

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 single, front-loaded sentence that wastes no words. It states exactly what the tool does in six words, making it one of the most concise entries possible for a status-check 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?

Given the tool's extreme simplicity—no parameters, no output schema, and a very low cognitive load—the description is nearly complete. It does not describe the response format, but for a ping/status tool, an agent can reasonably infer success from a non-error response. The absence of return details is a minor gap, so it does not get a 5.

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 accepts zero parameters, so the description needs to explain parameter semantics. The lack of any parameters is already fully captured by the empty input schema, and the description correctly implies the tool is a simple ping with no required inputs. The baseline of 4 applies here.

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 'Check CoinGecko API server status' uses a specific verb ('check') and resource ('CoinGecko API server status'), clearly distinguishing this health-check tool from the many market_coingecko_* siblings that fetch data. It is unambiguous and self-contained.

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 gives no guidance on when to use this tool versus alternatives like server_health, market_coingecko_global, or other ping-style tools. It does not state whether it is a prerequisite for other CoinGecko calls, nor does it mention any rate-limit or fallback considerations.

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