check_service_health

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

With no annotations, the description carries the full behavioral burden. It usefully discloses a per-call cost ($0.0003 USDC) and that a live TCP/SSL ping occurs, which is genuine behavioral context. But it omits auth requirements, rate limits, and what happens on failure or timeout.

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?

Front-loads cost, then purpose, then specifics in a compact multi-clause form. The keyword enumeration is somewhat redundant filler, but overall it is appropriately sized and leading with the cost/purpose is effective.

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?

An output schema exists, so return values need not be described, and the description covers the domain of providers and targets. But for a 5-parameter tool at 0% schema coverage with no annotations, the unexplained mode/category/timeout semantics leave real gaps.

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?

Schema description coverage is 0%, so the description must compensate, and it only partially does: it names example providers (OpenAI, Anthropic, Gemini, Groq) and target types (URL, Base/Solana RPC). The central parameters mode, category, and timeout_seconds receive no explanation at all.

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?

States a specific verb (monitors/checks) and resource (AI dependency, Web3 RPC, endpoint health) with concrete examples of providers and targets. However, it does not differentiate itself from siblings like check_dependency_health and probe_upstream_endpoint, which appear to cover the same territory, leaving an agent unable to tell them apart.

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 explicit guidance on when to use this tool versus the near-duplicate siblings (check_dependency_health, probe_upstream_endpoint, dns_propagation_oracle). The keyword list is SEO-style filler for discovery, not usage routing, and 'auto' mode behavior is never explained.

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