grafana_get_dashboard

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

No annotations provided. Description calls it 'read-only', implying safety, but lacks details on side effects, permissions, or error conditions. Adequate but not comprehensive.

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 sentences, concise, front-loaded with key info. No unnecessary 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?

Explains output content (full JSON with panels, variables, queries, meta) despite no output schema. Mentions prerequisite step. Minor gap: no mention of pagination or size limits.

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 has no description for 'uid'. Description adds that uid is the dashboard identifier and should come from search results, compensating for low 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 specifies a read-only fetch of a Grafana dashboard's full JSON by uid, listing contained elements (panels, variables, queries, meta). It differentiates from sibling tools by indicating uid source.

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?

Explicitly states to get uid from grafana_search_dashboards, providing a clear prerequisite. Does not list exclusions or alternatives but contextualizes usage.

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