set_data_lake_log_publishing

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

With no annotations, the description carries full burden. It discloses the SQL command executed, that it returns effective settings, and the error condition for unsupported endpoints. While it doesn't cover permissions or rate limits, it provides substantial behavioral transparency for a simple toggle tool.

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 front-loaded: first sentence states the purpose, then the SQL, then constraints, then parameters. Every sentence adds value without redundancy. It uses clear formatting with bulleted Args.

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 the tool's simplicity (3 required params, no nesting, output schema exists), the description covers the action, SQL, return value, supported environments, error behavior, and parameter meanings. No gaps are evident, and the output schema is referenced but not elaborated, which is appropriate since it exists separately.

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 parameter documentation in the Args section fully compensates. Each parameter is explained: workspace (name or GUID), item (warehouse name or GUID with restriction), and enabled (mapping boolean to AUTO/PAUSED). This adds significant meaning beyond the schema's type-only definitions.

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 'Enable or disable Delta Lake log publishing on a warehouse', providing a specific verb and resource. The tool is distinct from sibling set_* tools due to its unique resource name, and the SQL command is explicitly shown.

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 specifies that the tool is only supported on Fabric Data Warehouses and that SQL Analytics Endpoints are rejected with a ToolError, providing clear context. However, it does not mention alternatives or when not to use it versus other tools, though given the sibling list, no alternative exists for this specific setting.

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