target_scrape_health

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

The readOnlyHint annotation already establishes this is a safe read, and '[READ]' merely restates it. The description does add useful value by disclosing the return content (up/down summary plus unhealthy target list), but says nothing about scope, freshness, or pagination.

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?

Front-loaded with the read marker and the output summary, then a minimal Args block. No wasted prose, though the '[READ]' prefix is slightly redundant against the annotation.

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?

For a single optional-param tool with no output schema, the description covers the input and gives a rough sense of the return. It stops short of describing the summary format or how unhealthy targets are surfaced, leaving a modest gap.

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 0% schema description coverage, the description must carry the single parameter's meaning, and it does: 'target' is a Prometheus target name from config, and omitting it falls back to a default. That explains both the value source and the default semantics beyond the bare 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?

States a specific verb and resource: an up/down scrape-health summary plus the list of unhealthy targets. This distinguishes it from the more analytical sibling target_scrape_health_analysis, though the description never names that sibling to make the routing explicit.

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 indication of when to use this versus target_scrape_health_analysis, list_targets, or dropped_targets. The only guidance offered is the parameter default ('omit for the default'), which is param behavior, not tool-selection guidance.

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