superset_saved_query_delete

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

The description discloses that confirm_delete is a required confirmation, indicating the destructive nature of the operation. This adds behavioral context beyond the schema, which marks it optional with a default of false. However, it does not explicitly state that deletion is irreversible or describe any additional side effects.

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 concise, with a one-line purpose followed by a brief Args list. It is well-structured and front-loaded, with no unnecessary information.

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 simple delete tool with two parameters, the description covers the core functionality and the confirmation mechanism. However, it omits details about return values, permissions, and irreversibility, relying on the output schema and common sense. Given the lack of annotations, a bit more context would be beneficial.

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?

Both parameters are explained in the description: saved_query_id identifies the target, and confirm_delete is the deletion confirmation. This compensates for the 0% schema description coverage, though the description could clarify that confirm_delete should be set to true to actually delete.

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 begins with 'Delete a saved query', using a specific verb and resource. This clearly differentiates it from sibling tools like superset_saved_query_list, get, create, and update.

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?

No usage guidance is provided beyond the action itself. The description does not mention when to use this tool versus alternatives, nor any prerequisites or contraindications.

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