Search Dashboards

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

Annotations already declare this is a read-only, closed-world operation. The description adds useful scope context ('Empty query lists all') and the default space behavior, but does not disclose pagination, result limits, or authentication/permission needs beyond what annotations cover.

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 tightly structured sentences with the core purpose front-loaded and the space default clearly called out. No filler or redundant restatement of the name or schema.

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 a low-complexity, read-only search tool with an output schema and annotations, the description covers purpose, empty-query behavior, and the space default. It is nearly complete, but omits routing guidance versus get_dashboard and details about query matching.

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?

With 0% schema description coverage, the description compensates by explaining both parameters: query searches title/description and lists all when empty, and space targets a Kibana space by id with the default space as fallback. It leaves query matching semantics (substring vs. exact) and null handling implicit.

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 verb and resource ('Search dashboards') plus the search scope ('by title/description') and the empty-query behavior. However, it does not explicitly distinguish itself from the sibling get_dashboard, which likely retrieves a single dashboard by id.

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 implies usage through 'Search dashboards by title/description' and 'Empty query lists all,' but gives no explicit when-to-use guidance, no when-not conditions, and no named alternative such as get_dashboard for direct retrieval.

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