list_warehouses

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

With no annotations, the description must reveal behavioral traits. It discloses the overriding behavior of all_workspaces but omits potential details like pagination limits, permission requirements, or output format. Adequate but not thorough.

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?

Two sentences conveying purpose and key behavior with no extraneous information. Front-loaded and highly efficient.

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?

The description covers the primary parameter logic and scope. An output schema exists, so return values are documented elsewhere. Slight gap: no mention of prerequisites (e.g., workspace access). Mostly complete for a listing tool.

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%. The description adds meaning for the 'all_workspaces' parameter (its effect when true) but does not clarify the expected format or purpose of the 'workspace' parameter beyond being a workspace identifier. Partial compensation.

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 lists warehouses and SQL analytics endpoints, and explains the scope (workspace or all workspaces). It effectively distinguishes from sibling tools like list_sql_endpoints by combining both resource types.

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?

Provides guidance on when to use the 'all_workspaces' parameter but does not explicitly indicate when to favor this tool over siblings that list only one resource type (e.g., list_sql_endpoints). Implied usage, but lacks explicit alternatives.

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