get_dashboard

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

Annotations already declare readOnlyHint=true, and the description is consistent with that. The description adds the output fields and the space targeting behavior, but does not disclose potential errors, permissions, or limitations of what 'summary' includes. Given annotations cover the safety profile, the description adds modest but not rich behavioral context.

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, no filler. The first sentence states purpose and output, the second explains a parameter; both are necessary and the most important information is front-loaded.

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 get-by-id tool with output schema and annotations, the description covers the essential purpose and parameter semantics. It doesn't address usage relative to siblings or potential edge cases, but those are not critical given the low complexity and available schema.

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 descriptions (0% coverage). The description explains the non-obvious `space` parameter by stating it targets a Kibana space by id and defaults to the default space. `dashboard_id` is not described but its meaning is self-evident from the parameter name and tool name; still, a brief mention would be better. This partially compensates for the schema 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 the specific verb 'Get' and names the resource 'dashboard', and specifies the returned contents: 'title, description, and its panels'. This clearly distinguishes it from sibling search_dashboards and create_dashboard by being a targeted read operation on a single dashboard.

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 explicit when-to-use or comparison with alternatives is provided. The description implies the tool is for retrieving dashboard details, but it does not say when to prefer get_dashboard over search_dashboards or how the space parameter interacts with search. Thus usage guidance is only implied, not explicit.

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