superset_dashboard_get

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

With no annotations provided, the description carries the full burden. It discloses the 404 error for missing IDs and highlights the prerequisite that IDs come from dashboard_list. While it does not explicitly state read-only behavior, 'Get' implies it, and the presence of an output schema covers return-value details. This is meaningful behavioral context beyond the schema.

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 succinct: three sentences plus an Args line. The main purpose is front-loaded, the important usage note is highlighted with 'IMPORTANT', and every sentence adds value without repetition. Ideal length for a single-parameter getter.

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 single-parameter GET tool with an output schema, the description covers all essential operational aspects: how to obtain a valid ID, the 404 error behavior, and the core action. It does not need to explain return fields since the output schema exists. No significant gaps.

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 provides only 'dashboard_id' as an integer with zero description. The description compensates by specifying 'Dashboard ID (integer from dashboard_list result)', clarifying the source and expected format. This fully addresses the missing schema description, though it could add more about the ID's role (e.g., required, no default).

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's function: 'Get detailed information about a dashboard by ID.' The verb 'Get' is specific, the resource is a dashboard, and the qualifier 'detailed' distinguishes it from dashboard_list. It is unambiguous and differentiates among siblings by emphasizing ID-based lookup.

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 provides explicit usage guidance: 'if the ID is unknown, first call superset_dashboard_list to find the desired dashboard.' It also warns about the 404 behavior for non-existent IDs, which informs when not to use the tool directly. This is clear, actionable, and names the alternative tool.

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