dropped_targets

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

With no annotations, the description must disclose behavioral traits. It only states that targets are discovered but dropped by relabeling, and includes [READ] as a safety hint. It does not mention authentication, rate limits, pagination, return format, or any side effects. This minimal information is insufficient for a tool with no annotation support.

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 description is compact and well-structured, with a clear [READ] tag, a one-line summary of the resource, and a labeled Args section. Every sentence adds value without redundancy.

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?

Given the simplicity (one optional parameter, no output schema, no annotations), the description covers the core purpose and parameter semantics. However, it omits usage context relative to siblings and any return format details, leaving some gaps for an agent deciding when to invoke it.

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%, so the description carries the full burden. It explains that 'target' is a Prometheus target name from config and that omitting it uses a default. This adds meaningful context beyond the schema, which only defines a string with null 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?

The description clearly identifies the resource as 'Targets discovered but dropped by relabeling' and prefixes with [READ], indicating it returns information. It distinguishes from sibling tools like list_targets by specifying the 'dropped' subset, though it lacks an explicit verb like 'list' or 'get'.

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?

The description provides no specific guidance on when to use this tool versus alternatives. It does not mention list_targets or other target-related tools, nor does it state situations where this tool is preferred or not appropriate. The only guidance is the parameter explanation, which is not usage context.

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