grafana_search_dashboards

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

With no annotations, the description carries full burden. It states 'Read-only' indicating no mutation, and lists return fields. However, it does not disclose behavior like pagination, case sensitivity of subtitle search, or what happens when no query/tags are provided (likely returns all dashboards within limits). The limit parameter is mentioned in schema but not in description.

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: first states purpose and return fields, second links to the sibling tool. Every sentence adds value, no wasted words.

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 3 parameters, no output schema, and no annotations, the description adequately covers purpose, return fields, and how to proceed for full details. Missing details like result count or explicit handling of empty search are minor gaps for a search tool.

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?

Schema coverage is 67% (tags and query described, limit not). The description combines query and tags with 'and/or', clarifying how they interact, which adds meaning beyond the schema. Limit is not addressed but has clear constraints in schema.

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 performs a read-only search of Grafana dashboards by title substring and/or tags, and lists the returned fields (uid, title, folder, tags, url). This distinguishes it from the sibling grafana_get_dashboard, which fetches full dashboard JSON.

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 guides the agent to use grafana_get_dashboard with the uid for full dashboard details, providing a clear alternative. However, it does not specify when to avoid using this tool, e.g., if needing other data types or filtering by fields not supported.

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