drop_security_predicate

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

Without annotations, the description carries full burden. It discloses the underlying SQL command and notes that Fabric Data Warehouse supports only FILTER predicates, referencing a GitHub issue. However, it omits permissions, side effects, or reversibility, leaving gaps in behavioral understanding.

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: a clear action sentence, a technical detail paragraph, and an Args list. It is well-structured and free of unnecessary content, though the Args list could be integrated into the prose.

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 no annotations, the description covers the core action and SQL details. It references a GitHub issue and explains the lack of predicate-type parameter. However, it does not cover prerequisites (e.g., policy existence), error scenarios, or output behavior, leaving some contextual gaps.

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 description must compensate. It lists all five parameters in an Args block and adds format info for policy_name ('"schema.name" or "name"'). Other parameters have no added semantics beyond their names, which is acceptable but not fully compensating.

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 action: 'Drop the FILTER predicate from an existing row-level security policy.' It distinguishes from related tools like add_security_predicate and drop_security_policy by specifying the exact operation on a predicate.

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 explicit guidance on when to use this tool versus alternatives (e.g., drop_security_policy or set_security_policy_state). The description mentions technical constraints but does not provide usage scenarios or prerequisites.

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