grafana_search_dashboards

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

No annotations are provided, and the description only states the action and visibility constraint. It does not disclose pagination behavior, result format, search semantics, or any side effects. The brief mention of service account visibility adds minimal 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 a single concise sentence with no redundant wording. It is front-loaded with the action verb, making it easy to scan. However, it is extremely brief, which impacts completeness more than conciseness.

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 too sparse. It does not explain how the search behaves, what fields are searched, the meaning of the limit parameter, or the response structure. An agent would lack critical information for correct invocation and interpretation.

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 input schema has two parameters (limit, query) with zero documentation in the schema or the description. The description provides no explanation of what the query matches or how limit affects results, failing to compensate for the 0% schema coverage.

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 identifies the action (Search), the resource (Grafana dashboards), and the access scope (visible to the configured service account), distinguishing it from the sibling grafana_get_dashboard.

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 some context (searchable scope) but does not explicitly state when to use this tool versus grafana_get_dashboard or other search tools. No alternatives or exclusions are mentioned, so it relies on implicit understanding.

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