grafana_get_dashboard

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

The verb 'Get' adequately signals a read-only operation, and no annotations are provided to contradict that. Yet the description adds no detail on authentication requirements, error behavior (e.g., not found), or whether the full dashboard JSON model is returned, so transparency is minimal.

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 that front-loads the action and object. Every word contributes meaning and there is no redundancy.

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 simple, one-parameter read operation, this description is nearly complete: it states what is fetched and how. It could mention the response type or behavior when the UID does not exist, especially since no output schema is provided, which prevents a 5.

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 maps the 'uid' parameter to a dashboard identifier, which is helpful given the schema has no description for the property. However, it does not explain where the UID comes from or any format constraints beyond the schema's minLength, leaving some semantic gap.

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 uses a specific verb ('Get'), names the resource ('Grafana dashboard'), and identifies the lookup mechanism ('by UID'). This clearly distinguishes it from the sibling grafana_search_dashboards, which searches for dashboards rather than fetching by a known identifier.

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?

It clearly implies use when you already have a dashboard UID, which is a useful selection signal. However, it does not explicitly state when not to use it or point to grafana_search_dashboards for finding UIDs, so it stops short of full guidance.

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