superset_rls_delete

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses that deleting an RLS rule lifts restrictions for associated roles and highlights the severe security risk of deleting deny-by-default rules (clause='1=0'), which would expose ALL data. It does not mention irreversibility or permissions, but the disclosed risk is meaningful and goes beyond the bare delete action.

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 and well-structured: a clear one-sentence purpose, a prominent CRITICAL warning, and a compact Args list. No redundant or filler content. Each sentence earns its place, and the most important safety information is front-loaded with ALL CAPS emphasis.

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 that an output schema exists, the description need not explain return values. It covers the tool's purpose, the key security risk, and all parameter semantics. However, it would benefit from explicitly stating that confirm_delete must be set to true to actually perform the deletion, since the schema default is false and the description only marks it as 'REQUIRED'.

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?

Schema description coverage is 0%, so the description compensates by providing an Args section. It explains rls_id as the ID of the RLS rule to delete and confirm_delete as a required deletion confirmation. It also introduces the domain-specific concept of clause='1=0' for deny-by-default rules. This adds significant meaning beyond the raw schema which only gives types and a 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 opens with 'Delete an RLS rule' which is a specific verb+resource statement. It clearly distinguishes this tool from siblings like superset_rls_create, superset_rls_update, and superset_rls_get by stating the delete action and its immediate effect on role restrictions.

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 through the verb 'delete' and explains the consequence, but it does not explicitly state when to choose this tool over alternatives like superset_rls_update or provide any exclusion criteria. The critical warning serves as a caution rather than a usage guideline. No alternative tools are mentioned.

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