check_stack_status

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

With no annotations, the description must carry the behavioral burden; it does disclose the target layer (Docker-based services) and what is verified (reachability and correct configuration), which is meaningful context. It does not state that the call is read-only/non-mutating, nor what happens when a service is down (error vs. degraded status), leaving the safety and failure profile implicit.

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?

Two short sentences, front-loaded with the resource scope. The second sentence adds real detail (Docker-based, configured) rather than restating the first, though 'diagnostic tool' is mild filler.

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 no explanation, and there are no parameters to document. The description covers scope, component list, and the layer being probed; the only remaining gap is the read-only/no-side-effect assurance for a diagnostic call.

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 takes zero parameters and the schema is a closed empty object, so there is nothing for the description to disambiguate. Baseline 4 applies.

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 (check) and resource (health and connectivity of the observability stack) and enumerates the components covered: Loki, Prometheus, Grafana. That scope implicitly separates it from generic siblings like monitor_system_resources and monitor_server_health, but it never names or explicitly rules out those alternatives.

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?

Calling itself a 'diagnostic tool' that verifies reachability implies the use case (troubleshooting connectivity/configuration), but there is no explicit when-to-use statement, no prerequisites, and no guidance on choosing it over show_status_dashboard, observability_stack_health_card, or monitor_server_health.

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