service_health

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

Discloses that no authentication is required, the endpoint is a public GET /health, and returns per-dependency check results. Without annotations, this provides adequate transparency, though the dependency list is not specified.

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 sentences, zero wasted words. The first sentence front-loads the primary purpose and differentiation, and the second adds details and alternative usage. Highly efficient.

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 simplicity of a no-parameter health check, the description is largely complete. It covers what, how, and auth. However, it does not specify the return format or error handling, which could be clarified.

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?

With no parameters in the schema, the description adds all necessary meaning by explaining the tool's operation. No parameter documentation is needed, and the description fully compensates for the empty schema.

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 clearly states it is a liveness check for the Run402 SERVICE, explicitly distinguishing it from organization status checks. It uses a specific verb ('liveness check') and resource ('Run402 SERVICE'), and differentiates from the sibling 'status' tool.

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?

Provides explicit guidance on when not to use this tool ('not your organization') and directs to the alternative 'status' tool for organization status. This helps agents choose correctly among siblings.

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