List Kibana data views

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

Without annotations, the description carries the burden, and it discloses the key behavioral constraint: 'works with Kibana-level privileges only' and the reliability context when ES cluster APIs are forbidden. It doesn't detail output fields or error behavior, but for a zero-parameter read-only list operation, the core behavioral traits are 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?

Two concise sentences with no filler: the first names the operation and resource, the second adds the privilege and use-case context. The key scoping phrase 'active space' is front-loaded.

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 simple no-parameter list operation, the description covers what is listed, where it runs, and when to prefer it over cluster-level tools. No output schema exists, but the verb 'List' sufficiently implies the return value, and no further configuration or parameter details are 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?

Input schema has zero properties, so there are no parameter semantics to clarify; per baseline this is a 4. The description's mention of 'active space' provides the only relevant scope context an agent needs.

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 uses a specific verb and object: 'List the Kibana data views (index patterns) available in the active space.' It also distinguishes itself from ES cluster-index tools by noting it relies on Kibana-level privileges, so an agent can tell it apart from siblings like es_list_indices.

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?

It gives clear context: this works under Kibana privileges and is 'the reliable way' when Elasticsearch cluster APIs are forbidden. It does not explicitly name an alternative tool or list exclusions, but the implied when-to-use condition is strong.

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