get_dashboard_info

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

With no annotations provided, the description carries the transparency burden. It discloses that the tool returns a summary ('lightweight', 'without full panel definitions') and lists the contents of the response, but it does not explicitly state read-only or side-effect-free behavior, though the name 'get' implies an idempotent retrieval.

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 well-structured and front-loaded with the primary purpose, followed by usage tips and return details. It is slightly repetitive (e.g., mentioning 'without full panel definitions' and later 'basic info'), but overall remains concise and easily scannable.

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 description is complete for a getter of this complexity: it explains what it does, when to use it, and the parameters. Since an output schema is present, the return value description is sufficient, and no critical information is missing for correct invocation.

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 description includes an 'Args' section that explains each parameter: 'connection_name: Name of the Grafana connection' and 'dashboard_uid: UID of the dashboard'. This adds meaningful context beyond the bare schema, which has no descriptions, fully covering the parameter semantics.

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 retrieves lightweight dashboard metadata and a panel list, using the specific verb 'Get' with a precise resource. It distinguishes itself from sibling tools by explicitly mentioning 'without full panel definitions' and pointing to get_dashboard_panel for full details, ensuring no ambiguity.

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 explicit usage guidance, calling it the 'RECOMMENDED first step for exploring dashboards, especially large ones,' and instructs to use get_dashboard_panel for specific panel details. This clearly communicates when to use this tool and when to choose an alternative.

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