superset_get_dashboard

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

The description discloses what the tool returns ('full detail including position_json and json_metadata (filters)'), which is useful behavioral context. However, with no annotations provided, it carries the full burden and does not mention permissions, error handling, or that it is a read-only operation. It only partially covers the behavioral traits.

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 two concise sentences, front-loaded with the primary purpose ('Get a dashboard by id or slug') followed by a high-value detail on the return content. Every word earns its place, and there is no redundancy or 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?

Given the tool's simplicity (one parameter, clear output schema), the description is largely complete. It covers the input semantics, operation, and key return fields. Missing context includes explicit guidance on when to use it versus listing dashboards, but this is not critical for correct invocation.

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 schema has a single string parameter 'id_or_slug' with no description. The tool description compensates by explaining it accepts 'id or slug', which is essential semantic meaning beyond the schema. It could add examples or format constraints, but for a single parameter, this is adequate.

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 operation: 'Get a dashboard by id or slug.' It uses a specific verb (Get) and resource (dashboard), and distinguishes itself from siblings like superset_list_dashboards (listing) and superset_get_dataset (different resource). The mention of 'full detail' further clarifies its role as a retrieval tool for 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?

Usage is implied by the description: you use this when you have a dashboard's id or slug and need full detail. However, it does not explicitly mention alternatives or exclusions (e.g., 'use list_dashboards to find dashboards first'). It provides no 'when-not-to-use' guidance, placing it between implied usage and clear context.

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