ecosystem_health

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

The description states the behavior: checking health and returning a summary of reachability and responsiveness. However, with no annotations, it lacks details on side effects (assumed read-only), safety, or performance impact. It adds moderate value beyond the tool name.

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, front-loaded with verb and resources, second sentence clarifies output. No unnecessary words; efficient and clear.

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?

Tool has no parameters and an output schema, so description is complete enough. It identifies components and output nature, and the output schema presumably details the return format. No 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?

No parameters in input schema, so description cannot add parameter semantics. Baseline of 4 is appropriate given no parameters exist and description does not need to explain them.

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 the verb 'Check health' and specifies the resource 'all ecosystem components' with explicit list (OpenSIPS, Homer, RTPEngine, CP). This distinguishes it from sibling tools like 'ecosystem_overview' or 'health_check' by being component-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?

No explicit guidance on when to use this vs alternatives. For example, there is no mention of when to use this over 'ecosystem_overview' or 'health_check', nor any exclusions or context hints.

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