Check Rapid Indexer service health

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

Annotations already mark it read-only, idempotent, and non-destructive; the description adds value by explaining what the call actually performs—a ping, a feature report, and API key validation. This extra context helps the agent interpret success or failure. No contradiction with the annotations exists.

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 two compact sentences with no filler. The main action is front-loaded, and the parenthetical list of reported features is an efficient way to convey additional detail.

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 parameterless health-check tool with rich annotations and an output schema, the description covers the essential contract: what is pinged, what is reported, and that API key validation occurs. Return format details are handled by the output schema, so nothing critical is missing.

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 input schema has zero parameters, so there is nothing parameter-related the description needs to add. With no parameters to document, the baseline of 4 is appropriate, and the description does not introduce any ambiguity.

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 uses a specific verb ('Ping') and names the exact resource ('Rapid Indexer API'), then enumerates the specific outputs: version, enabled feature flags, and API key validity. This clearly distinguishes it from siblings like check_index_status, which is about URL indexing status rather than service health.

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 conveys a clear use case: verify that the Rapid Indexer API is reachable, learn which features are enabled, and confirm the configured API key works before relying on other indexer workflows. It does not explicitly name alternatives or exclusions, but the context is strong enough that an agent can judge when to call it.

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