dropped_targets

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

readOnlyHint=true already establishes this as a safe read, so the '[READ]' prefix is redundant. The description does add useful domain context: the drops come specifically from relabeling, not from scrape failures. It says nothing about return shape, pagination, or whether a config reload is involved.

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?

The purpose clause is front-loaded and wastes no words. The Args block is boilerplate but earns its place because the schema documents nothing about the parameter.

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?

With no output schema and 0% schema coverage, the description has to carry more than it does. It establishes what the tool returns conceptually and how to filter, but leaves the default target, the return structure, and the relationship to config reload undefined.

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?

Schema coverage is 0% and the schema carries no description for 'target', so the description is the only source of semantics. It explains that the value is a Prometheus target name from config and that omitting it selects the default. It stops short of defining which target is 'the default'.

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 resource and condition: targets that were discovered but dropped by relabeling. That is meaningfully distinct from the near-neighbors list_targets and target_scrape_health, so an agent can pick it out. It lacks an explicit verb, but the read-only listing intent is unmistakable.

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?

Usage is implied by the purpose (debugging relabel drops) rather than stated. No when-to-use or when-not-to-use guidance, and the close siblings list_targets and target_scrape_health are never contrasted. The only explicit guidance is the 'omit for the default' note on the argument.

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