list_workspaces

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

The description says 'all' but the input schema's 'active' parameter defaults to true, meaning by default only active workspaces are returned, not all. This misstatement is not disclosed. The description also does not mention the limit parameter, pagination, or return structure. The readOnlyHint annotation covers safety, but the behavioral claim is misleading.

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, concise sentence that front-loads the verb and resource. It contains no filler and 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?

The tool is simple, but the description omits critical context: the active filter default contradicts 'all', no explanation of limit, and no mention of what a 'configurable agent workspace' is or what the return format looks like. With no output schema, the description should provide more clarity.

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 50%; the 'active' parameter has a description but 'limit' only has a type. The description adds no clarification about 'limit' or how 'all' interacts with the active filter. It does not compensate for the undocumented parameter.

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 configurable agent workspaces' clearly identifies the verb (list) and resource (configurable agent workspaces), with a scope qualifier ('all'). This distinguishes it from siblings like get_workspace (single) and create_workspace (create).

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 implies usage as the broad listing tool for all configurable workspaces, but it does not explicitly state when to use this instead of get_workspace or create_workspace. No alternatives or exclusions are mentioned, making the guidance only implicit.

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