superset_query_get

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It describes a read operation ('Retrieve') but does not explicitly state that it has no side effects, nor does it mention error handling, permissions, or rate limits. The lack of any warning or safety information is a gap for a tool with no annotation support.

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 extremely concise: one sentence for purpose and one for the parameter. Every word earns its place, and the structure is front-loaded with the action, making it easy to parse quickly.

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 low complexity (one parameter, output schema exists), the description covers the essential purpose and parameter meaning. It could add a note about when to use this instead of other query-related tools, but overall it is sufficiently complete for a straightforward retrieval operation.

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 to the single parameter query_id by specifying its type ('integer') and its provenance ('from query_list result'). Since the schema provides only the type with no description, this compensates well for the 0% schema description coverage.

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 a specific verb ('Retrieve') and identifies both the resource ('detailed information about a query') and the lookup key ('by ID'). This clearly distinguishes the tool from sibling tools like superset_query_list (which lists queries) and superset_query_stop (which stops a query).

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 mention of 'integer from query_list result' implies a workflow where query_list is used first to obtain the ID, then query_get retrieves details. This gives clear contextual guidance on when to use the tool, though it doesn't explicitly state alternatives or when not to use it.

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