health_overview

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

Description states it makes 'one call' and returns aggregated data, but does not disclose potential performance impact, rate limits, or whether the call is read-only. With no annotations, the agent must infer safety from naming. Adequate but not comprehensive.

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 precise sentences with no filler. Purpose and return type are front-loaded, making it quick to parse.

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?

Without an output schema, the description outlines the structure (overall level, per-component, critical findings). This provides sufficient context for a health snapshot, though exact field names or formats are omitted.

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 exist, so schema coverage is 100% by default. The description confirms no params are needed, adding no further meaning. Baseline 4 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?

Description clearly states it is a full deployment health snapshot listing all components (gateway, resources, skill registry, etc.) and return types (overall HealthLevel, per-component breakdown, critical_findings list). This distinguishes it from sibling tools that focus on single components.

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 advises 'Use this first for a single-pane summary,' indicating it is the initial tool to invoke. However, it does not specify when to use sibling tools for deeper investigation, leaving some ambiguity.

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