list_workspace

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a listing operation, which implies read-only behavior, but doesn't disclose authentication requirements (though the schema shows ak/sk parameters), rate limits, pagination behavior (schema mentions page_size but description doesn't explain it), or what happens when no workspaces exist. The description is minimal and lacks important behavioral context.

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 a single, efficient sentence in Chinese that states the core purpose without unnecessary words. It's appropriately sized for a simple listing tool and front-loads the essential information. Every word earns its place.

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 this is a read operation with an output schema (which handles return values), the description's minimalism is somewhat acceptable. However, for a tool with authentication parameters and pagination options, the description should at least mention these aspects. The combination of no annotations, 0% schema description coverage, and a sparse description leaves significant gaps in understanding how to use this tool effectively.

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 must compensate for undocumented parameters. The description mentions no parameters at all, while the schema shows one required 'config' parameter with four sub-properties (ak, sk, endpoint, page_size). The description fails to explain what these parameters do, when they're needed, or how they affect the listing operation.

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 action ('列出' - list) and resource ('工作空间名称与描述' - workspace names and descriptions) with the scope '当前登录环境' (current login environment). It's specific about what information is returned (names and descriptions), but doesn't differentiate from potential sibling tools like 'create_workspace_bioos' or 'export_bioos_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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, when this tool is appropriate versus other workspace-related tools, or any exclusions. The context '当前登录环境' (current login environment) is the only contextual hint.

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