loki_list_containers

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It honestly reveals that the tool filters out ephemeral names and explains why, plus notes that filtered items are still accessible via other tools. It does not mention error conditions or auth requirements, but for a simple list operation, the filtering behavior is the key nuance and is well covered.

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 well-structured with a clear main sentence, a brief explanatory note about filtering, and a concise parameter definition. Every sentence adds value without redundancy, and it remains compact while covering key details.

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 tool's simplicity (one optional parameter) and the presence of an output schema, the description is complete. It covers the purpose, filtering behavior, lookback format, and alternative tools. No critical information for invocation or interpretation is missing.

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?

The schema provides only a `lookback` string with a default and no description. The description compensates fully by defining the parameter as a duration, providing example formats (`1h`, `24h`, `7d`), and restating the default. This gives the agent all necessary syntax and semantic meaning.

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 states the tool's action ('List') and specific resource ('durable container names actively logging in the lookback window'). It also distinguishes itself from siblings by mentioning that ephemeral names are filtered and pointing to `loki_list_label_values` for the raw unfiltered list, making the purpose unambiguous.

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 explicitly explains when to use this tool (for durable container names) and provides clear alternatives: ephemeral names remain queryable via `loki_query_range`, and raw unfiltered lists are available via `loki_list_label_values`. This gives the agent clear decision guidance.

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