service_health

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

Discloses it reads a public GET endpoint, returns per-dependency results, and requires no authentication. Since no annotations are provided, the description fully covers behavioral traits without gaps.

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?

Three concise sentences with front-loaded information. Each sentence adds unique value: purpose, sibling distinction, and operation details. No wasted words.

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?

Provides adequate context for a simple health check with no parameters. Mentions 'per-dependency check results' but lacks detail on exact response format. Without an output schema, a bit more structure could help, but overall sufficient.

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?

Input schema has 0 parameters, and schema coverage is 100% (empty). Description adds no parameter info because none exist. Baseline score of 4 applies per rules for zero-parameter tools.

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?

Clearly states it's a liveness check for the Run402 SERVICE, specifying it's not for the organization, and distinguishes from sibling `status` which handles organization status. The verb 'check' and resource 'service health' are specific.

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?

Explicitly says when NOT to use ('not your organization') and directs to alternative `status`. Also notes 'No auth required', making it clear when this tool is appropriate.

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