set_data_lake_log_publishing

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

With no annotations, the description carries the safety burden and does well: it reveals the exact SQL executed, the fact that the setting is read back after the change, and the endpoint rejection behavior. It stops short of mentioning permission requirements or broader side effects, but the core mutating behavior is unambiguous.

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: a one-line operation, the exact SQL, support constraints, then an Args section. The only minor redundancy is the repeated SQL Analytics Endpoints rejection, but it does not hurt readability.

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 small three-param toggle with an output schema, the description covers target compatibility, parameter semantics, error behavior, and the post-change readback. An agent has enough information to call it correctly without inspecting external docs.

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%, yet the description documents every parameter: workspace and item accept names or GUIDs, item excludes SQL Analytics Endpoints, and enabled maps True/False to AUTO/PAUSED. This fully compensates for the empty schema descriptions.

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 first line identifies the exact operation: enabling or disabling Delta Lake log publishing on a warehouse, and the description further pins it to the ALTER DATABASE CURRENT SET statement. This clearly distinguishes it from sibling setting tools like set_time_travel_retention or set_result_set_caching.

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?

States the supported target clearly ('Only supported on Fabric Data Warehouses') and explicitly warns that SQL Analytics Endpoints are rejected with a ToolError. It does not name alternative tools, but the constraint gives an agent clear go/no-go guidance.

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