list_workspaces

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only states 'List all workspaces' without detailing pagination, return format, whether archived workspaces are included, or any access requirements. This lack of detail does not inform the agent about what to expect beyond the minimal action.

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, front-loaded sentence with no redundant words. It conveys the essential purpose without any filler. This is appropriately concise for a tool with no parameters.

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?

The tool is simple, but the description omits what a 'list all' operation returns (e.g., a list of workspace objects vs. names, pagination behavior). Given there is no output schema or annotations, the description is not enough for an agent to understand the full context of the invocation and response. More information on the return structure would provide completeness.

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 has zero parameters, and schema description coverage is 100% (vacuously, as there are no properties). Since there are no parameters, the baseline is 4, and the description adds nothing that detracts from this. It correctly implies no filtering or options.

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 'List all workspaces' clearly states the action (list) and the resource (workspaces). It uses a specific verb and resource, distinguishing it from sibling tools like 'get_workspace' which implies retrieving a single 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?

No usage guidance is provided. The description does not mention when to use this tool versus alternatives such as 'get_workspace' for a single workspace or 'list_collections' for a different resource type. No exclusions or prerequisites are stated.

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