get_dashboard

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the type of information returned (cards, layout, settings), but this may overlap with the output schema. No additional behavioral traits (auth, rate limits, side effects) are disclosed, making this a minimal but acceptable addition beyond annotations.

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, well-structured sentence that front-loads the action and outcome. It is concise, informative, and every word adds value with 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?

Given the simplicity (one required parameter), read-only annotation, and presence of an output schema, the description adequately covers the tool's purpose and usage. The agent has enough context to invoke and interpret the response without needing further details.

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 coverage is 100%, with a single required parameter 'dashboard_id' described as 'The ID of the dashboard to retrieve.' The description adds 'specific dashboard' but doesn't provide further syntax or format details beyond the schema, so it meets the baseline but doesn't exceed it.

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 detailed information about a specific Metabase dashboard, listing contents (cards, layout, settings). This distinguishes it from sibling tools like list_dashboards (which lists all dashboards) and get_dashboard_cards (which likely retrieves just cards), providing a specific verb+resource+scope.

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 gives clear usage context: 'use this to examine dashboard structure or get configuration details' and specifies 'a specific Metabase dashboard,' implying use when you have a dashboard ID. It does not explicitly exclude alternatives like list_dashboards, but the context is sufficient for an AI agent to select it appropriately.

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