warehouses_list

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

The description adds the behavioral detail that an empty list is returned when no warehouses exist, which goes beyond the readOnlyHint annotation. However, it does not discuss potential pagination or ordering of results.

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 extremely concise, consisting of two short sentences that front-load the core purpose and then add a clarifying detail. Every sentence is necessary and informative.

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 tool with no parameters, the description covers the essential behavior. The presence of an output schema handles return value details, and the description mentions the empty list case. It is fully 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?

There are no parameters, and the schema coverage is 100%. The baseline for zero parameters is 4, and the description does not need to add parameter information. It is adequate.

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 the tool lists all SQL warehouses visible to the authenticated principal, using specific verb and resource. It distinguishes from sibling tools like warehouses_get (single) and warehouses_create by focusing on listing all visible entities.

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 no guidance on when to use this tool versus alternatives such as warehouses_get. While the purpose is clear, it lacks explicit instructions about circumstances to prefer this list tool over others.

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