List Workspaces

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds behavior those annotations cannot express: automatic workspace selection when a single match occurs, the fact that a module list is returned in that case, and that admin listing is scoped to own memberships unless `search` is passed. This is genuine disclosure beyond structured fields.

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?

Three front-loaded sentences, each carrying distinct information (purpose, call order/auto-selection, admin search behavior). No filler or repetition of the title.

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?

No output schema exists, yet the description explains the meaningful return case (module list returned on single match) and the routing decision that follows. For a zero-required-parameter read tool, nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so baseline is 3, but the description adds meaning the schema does not: `search` changes admin behavior from listing own memberships to finding any workspace by name. It clarifies semantics of the optional filter well beyond the schema's 'case-insensitive name filter'.

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?

States a specific verb and resource ('List workspaces the current user has access to') and bounds the scope to accessible workspaces. This is easily distinguishable from siblings like list_modules or set_workspace.

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?

Explicitly says it is 'typically the first call of a session' and names the branch condition: if exactly one workspace matches, no set_workspace or list_modules is needed; otherwise call set_workspace next. It also distinguishes admin behavior of `search`. Alternatives and exclusions are given, not inferred.

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