list_sql_pools

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

With no annotations provided, the description carries full burden. It adds the admin role requirement and beta API note, but fails to disclose other critical traits such as read-only nature, pagination behavior, or any side effects. The description is minimal.

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 comprised of two concise sentences, front-loaded with the core purpose. Every sentence provides essential information without redundancy or filler.

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 simple list operation with an output schema, the description covers basic purpose and prerequisites but lacks parameter details and behavioral nuances. It is minimally viable but leaves room for improvement.

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 must compensate. It mentions 'workspace' in context but provides no additional meaning about the parameter format (e.g., name vs ID) or constraints. The agent receives no help beyond the schema definition.

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 'Return the list of custom SQL pools for a workspace,' which is a specific verb-resource combination. It distinguishes from siblings like 'get_sql_pool' (single pool) and 'create_sql_pool' (mutation) by focusing on listing.

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 mentions the prerequisite of workspace admin role and the beta/preview status, which provides some context. However, it does not explicitly guide when to use this tool versus alternatives like 'list_sql_pool_insights' or 'get_sql_pool'. Usage is implied but not fully clarified.

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