list_workspaces

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

Disclosed the core behavior: returns accessible workspaces and filters based on configuration. No annotations exist, so description carries the burden. Lacks details on side effects or auth needs but is sufficient for a read-only list operation.

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, front-loaded with the main action, no unnecessary words. 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?

Given no parameters and an existing output schema (implied), the description fully covers what the tool does. The addition of the allowlist behavior is helpful.

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?

No parameters defined, so schema coverage is 100%. The description adds value by mentioning the environment variable configuration, but parameter semantics are inherently not applicable.

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 Fabric workspaces the caller has access to. It distinguishes from sibling 'get_workspace' by implying a bulk listing vs single retrieval, and adds detail about the optional allowlist filtering.

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 clear context for listing all workspaces and mentions a configuration condition (allowlist). However, does not explicitly state when not to use it or compare to alternatives like 'get_workspace'.

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