list_workspaces

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

With no annotations provided, the description carries the behavioral burden. It implies read-only behavior through 'List' and discloses that it returns a string or an error message. However, it does not clarify the scope of 'available' workspaces, required permissions, or output formatting, leaving meaningful gaps.

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 compact and front-loaded with the core purpose, and the Returns line adds useful information. The 'ctx' line contributes little value for an MCP caller and feels somewhat unnecessary, but the overall structure is clean and readable.

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 zero-parameter listing tool, the description provides the basic purpose and return behavior, which is close to sufficient. However, absent annotations and an output schema, it could better explain what 'available' means and how this tool fits with workspace-related siblings like set_workspace.

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 input schema is empty, so the 0-parameter baseline applies. The description mentions a 'ctx' argument, but it is not reflected in the schema and is described only generically as a context object. Since there are no actual agent-supplied parameters, the baseline of 4 is appropriate.

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 states 'List all available Fabric workspaces,' giving a specific verb and resource. This clearly distinguishes it from sibling tools like create_workspace and set_workspace. There is no ambiguity about what operation the tool performs.

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 set_workspace, create_workspace, or list_warehouses. Usage context must be inferred entirely from the tool name and sibling list, which is insufficient for an agent.

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