Get Dashboard

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that — no note on what the 'include' expansion does, whether missing dashboards error or return empty, or cross-organization access behavior. An output schema exists, so return-value detail is not required.

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?

A single front-loaded sentence with zero waste, correctly scoping the tool to one resource. It is very terse, but nothing in it is filler.

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?

With annotations and a full output schema present, the remaining gap is the undocumented 'include=panels' option and no routing guidance against list_dashboards. For a simple single-resource getter this is minimally adequate but leaves the agent to discover the panel-expansion behavior on its own.

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 description coverage is 100% and the 'id' param already documents UUID-vs-slug formats and the naming pitfall; the description only restates 'by id'. The optional 'include' enum is never explained in the description, but the baseline of 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource ('Retrieves a specific dashboard by id'), which is clearly distinguishable from list_dashboards and get_dashboard_panel. It does not explicitly name the sibling it differs from, but the singular-resource scope is unambiguous.

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?

No guidance on when to use this versus list_dashboards or get_dashboard_panel, and no mention of prerequisites or when the optional 'include=panels' expansion is appropriate. The agent must infer usage entirely from the name and schema.

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