get-targets

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states 'Get information about targets' without mentioning whether this is a read-only operation, what permissions might be required, whether it returns paginated results, or what format the information comes in. For a tool with no annotation coverage, this is insufficient behavioral context.

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 extremely concise at just four words, which is efficient. However, this conciseness comes at the cost of being under-specified rather than appropriately sized. The single sentence doesn't waste words but fails to provide necessary context.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'targets' are in this context, what information is returned, or how this tool relates to the sibling Prometheus-related tools. For a tool in what appears to be a monitoring system context, more explanation is needed.

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 description coverage is 100%, so the schema already fully documents the single parameter 'state' with its enum values and description. The description adds no additional parameter information beyond what the schema provides, which meets the baseline expectation when schema coverage is complete.

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 'Get information about targets' states a general purpose but lacks specificity. It mentions the verb 'Get' and resource 'targets', but doesn't clarify what kind of information is retrieved or how this differs from sibling tools like 'get-alerts' or 'get-series'. The purpose is vague rather than 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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'get-alerts', 'get-rules', and 'get-series' available, there's no indication of when this tool is appropriate versus those others. No context or exclusions are mentioned.

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