search_dashboards

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

Annotations already indicate readOnlyHint=true, so the description adds value by explaining the effect of an empty query (lists all dashboards) and the default space behavior. These are behavioral details not present in the schema or annotations. However, it does not describe pagination, result limits, or other side effects, which keeps it at a moderate level.

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, consisting of three short, front-loaded sentences. The first sentence states the core purpose, the second clarifies a key behavior, and the third explains a parameter. No unnecessary words or fluff.

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 search tool with an output schema and read-only annotation, the description covers the essential aspects: what it searches, how to list all, and the space-scoping parameter. It omits potential details like sorting or result limits, but given the output schema and the tool's simplicity, it is sufficiently complete.

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 has no descriptions (coverage 0%), so the description fully compensates by explaining both parameters: 'query' searches by title/description, and 'space' targets a Kibana space by id with a default. It also clarifies the default values and behavior, adding meaning far beyond the plain type definitions.

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 purpose: 'Search dashboards by title/description.' It uses a specific verb and resource, and distinguishes this from sibling tools like get_dashboard (which retrieves a specific dashboard) and create_dashboard (which creates one). The mention of empty query behavior further clarifies its scope as a listing/search operation.

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 when to use this tool (when searching by text) and provides clear context about the query and space parameters. It does not explicitly mention alternatives or exclusions, but the context is sufficient for an agent to decide to use this over other singular dashboard tools. The note about empty query listing all is a usage hint.

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