list_warehouses

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses that the call returns a string containing the list or an error message, and that workspace is optional, but it does not explicitly confirm the operation is read-only or describe what happens when workspace is null.

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 short, front-loaded, and follows a clean Args/Returns structure. The first sentence states the core purpose immediately, and there is little wasted text, though the ctx line adds minimal agent-facing value.

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 optional-parameter list operation, the return type is disclosed and there is no output schema to rely on. The main gap is the meaning of omitting workspace, which is relevant for a correct first invocation given the set_workspace sibling 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?

The schema has no parameter descriptions (0% coverage), so the Args section is the only semantic source for parameters. It adds that workspace accepts a name or ID and is optional, and it mentions ctx; this is sufficient to construct a basic call, though the null-workspace behavior remains implicit.

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 opens with a specific verb-resource pair, "List all warehouses," and scopes it to "a Fabric workspace," which clearly distinguishes it from sibling tools like list_lakehouses, list_tables, create_warehouse, and set_warehouse. The purpose is unambiguous.

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 gives no explicit guidance on when to use this tool versus sibling list tools, nor does it explain when to provide or omit the optional workspace parameter. It also does not state whether omitting workspace falls back to the active context, so the agent must infer the intended invocation pattern.

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