Superset MCP Integration

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the API endpoint and that it 'retrieves information about a saved SQL query,' which implies a read-only operation, but doesn't explicitly state this is a safe read operation. It lacks details about authentication requirements, rate limits, error conditions, or what happens if the query_id doesn't exist. The description adds some context about what information is returned but doesn't fully compensate for the lack of 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 appropriately sized with three clear sections: purpose statement, API endpoint context, and parameter/return documentation. Each sentence adds value without redundancy. The structure with 'Args:' and 'Returns:' headings is helpful, though the formatting could be slightly cleaner. There's no wasted verbiage.

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 read operation with no annotations and no output schema, the description provides adequate basic information about what the tool does and what parameter it requires. However, it lacks details about authentication requirements, error handling, rate limits, and the complete structure of the returned dictionary. The mention of 'including SQL text and database' gives some output context but doesn't fully compensate for the missing output 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?

The description adds meaningful context for the single parameter: 'query_id: ID of the saved query to retrieve.' With schema description coverage at 0% (the schema only shows 'Query Id' as title with no description), this parameter documentation in the description is essential. It clarifies that this is an identifier for retrieving a specific saved query, though it doesn't specify format constraints or where to obtain valid IDs.

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 purpose as 'Get details for a specific saved query' with the specific verb 'Get' and resource 'saved query'. It distinguishes from sibling tools like 'superset_saved_query_create' and 'superset_sqllab_get_saved_queries' by focusing on retrieving details for a single query by ID rather than creating or listing queries. However, it doesn't explicitly differentiate from 'superset_query_get_by_id' which appears to serve a similar purpose for different query types.

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 implies usage context by specifying it retrieves 'a specific saved query' and mentions the query_id parameter, suggesting this should be used when you have a known query ID. However, it provides no explicit guidance on when to use this versus alternatives like 'superset_query_get_by_id' or 'superset_sqllab_get_saved_queries', nor does it mention prerequisites or exclusions.

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