superset_database_delete

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

With no annotations, the description bears full burden. It clearly discloses critical side effects: 'breaks ALL datasets, charts, and dashboards using this DB' and notes associated datasets become broken. This goes beyond the basic delete action and is essential for safety.

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 compact and front-loaded with the purpose, followed by a critical warning and parameter list. It slightly repeats the cascading breakage information but remains overall efficient and well-structured.

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?

The description covers the action, side effects, and parameters adequately. An output schema exists, so return values need not be explained. The main gap is missing details on behavior when confirm_delete is omitted or false, but the critical warning and parameter list provide enough context for a destructive 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 explains both parameters: database_id as the connection ID and confirm_delete as deletion confirmation. However, calling confirm_delete 'REQUIRED' conflicts with the schema, where it is optional with a default of false. This adds meaning but also introduces ambiguity about whether it must be provided or set to true.

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 'Delete a database connection' with a specific verb and resource, distinguishing it from sibling tools like database_update or dataset_delete. The scope is precise and unambiguous.

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 use is for deleting a database connection but does not explicitly state when to use this tool over alternatives or provide exclusion criteria. No alternatives are mentioned, and the cascading warning serves as precaution rather than usage guidance.

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