set_result_set_caching

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

With no annotations provided, the description carries the full behavioral burden. It transparently discloses that the tool executes ALTER DATABASE CURRENT SET RESULT_SET_CACHING { ON | OFF } and returns the effective settings read back after the change, which is valuable behavioral detail beyond what the schema shows.

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 well-structured and front-loaded, with the core action stated first and details organized logically. The only minor flaw is that the SQL Analytics Endpoints rejection is mentioned twice: once in the main description and again under the item parameter, which is slightly redundant.

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 3-parameter boolean-setting tool with an output schema present, the description is complete. It covers the action, the specific SQL behavior, target identification, the enabled flag semantics, and the critical unsupported endpoint case. Nothing essential is missing for an agent to invoke it correctly.

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 fully compensates. Every parameter is explained: workspace as name or GUID, item as warehouse name or GUID with an explicit rejection note for SQL Analytics Endpoints, and enabled mapped to True/False for enabling/disabling. This is clear, actionable parameter documentation.

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 a specific verb and resource: 'Enable or disable result-set caching on a warehouse.' It also names the exact SQL statement executed, making the tool's function unambiguous and distinguishable from sibling tools like clear_cache or get_warehouse_settings.

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 provides clear context for when the tool applies by specifying that it is only supported on Fabric Data Warehouses, not SQL Analytics Endpoints, and that unsupported endpoints are rejected with a ToolError. It does not explicitly name alternative tools for inspecting or clearing caching, but the supported/unsupported distinction is strong usage guidance.

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