disable_sql_pools

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

Despite no annotations, the description discloses that pools are disabled, configuration is preserved, re-enabling is possible, and it targets a beta/preview API. It could benefit from noting effects on active queries or connections, but overall adequate.

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?

Three concise sentences, each adding distinct value: action, re-enabling note, and prerequisites. No wasted words.

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?

Covers core functionality, prerequisites, and re-enabling pathway. Lacks details on error handling or asynchronous behavior, but for a simple toggle tool with output schema present, it is reasonably complete.

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%, and the description only implies workspace is the target in the tool purpose, providing no additional meaning or format guidance for the single required parameter.

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 it disables custom SQL Pools while preserving configuration, distinguishing it from deletion tools like delete_sql_pool and its sibling enable_sql_pools.

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?

It mentions that re-enabling restores configuration via enable_sql_pools and requires workspace admin role, providing good guidance on when to use and prerequisites, but does not explicitly exclude misuse (e.g., permanent disable).

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