Workspace List Workspaces

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered externally. The description adds only that pagination is supported, which is modest extra context, and it does not describe ordering, result volume, or the page-token lifecycle.

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 compact sentences with the core purpose front-loaded and no filler. It is efficient, though the second sentence is too thin to be fully load-bearing.

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?

An output schema exists, so return values need not be explained. However, for a paginated list tool with 0% parameter documentation, the description leaves the agent guessing about pagination mechanics and result limits, which is the minimum-viable level rather than 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?

Schema description coverage is 0%, so the description carries the burden. It mentions "page token" (roughly the 'page' parameter) but does not explain the token format, whether it is opaque, or what the 'limit' parameter (default 200) does or its bounds. Only a vague hint at one of two parameters.

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?

"List all workspaces" gives a specific verb and resource, and among the siblings it is the only tool that enumerates workspaces (the others are get/create/delete workspace or list other resources like files, tags, grants). It is clear but does not explicitly distinguish itself from related listing tools such as workspace_get_workspace or the *list_all_* variants.

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 states what the tool does but gives no when-to-use context, no prerequisites, and no alternatives (e.g. workspace_get_workspace for a single workspace). The agent must infer usage from the name alone.

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