list_dashboards

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

No annotations are provided, so the description carries the full burden. The '[READ]' tag implies read-only behavior, but the description does not disclose return format, pagination, auth needs, or other behavioral traits. For a simple list operation, this is somewhat adequate but lacks depth.

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, with a clear front-loaded [READ] tag and resource, followed by compact argument explanations. Every sentence adds value and there is no redundant or filler content.

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?

The tool has no output schema, yet the description does not explain what is returned (e.g., list of dashboards, metadata, full configs). It also omits pagination or limit behavior. While the two parameters are well covered, the return value is left ambiguous, leaving an agent to guess the response shape.

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 no descriptions, but the description's Args section explains 'query' as an optional title substring and 'target' as a Grafana target name from config. This compensates for the 0% schema coverage and adds meaningful semantics beyond the basic schema types.

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 it lists Grafana dashboards and supports an optional title query. It is specific with the verb 'list' and resource 'Grafana dashboards', though it does not explicitly differentiate from sibling tools like get_dashboard or list_folders.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention that get_dashboard should be used for a single dashboard or that list_folders is for folders, nor any conditions or exclusions.

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