list_workspaces

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

No annotations are present, so the description should disclose behavioral traits. It only states 'List active workspaces', which implies a read-only operation but does not explicitly say so, nor does it define 'active' or mention any side effects, auth needs, or rate limits. The description adds minimal context beyond the verb itself.

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?

A single, front-loaded sentence with no wasted words. It clearly states the action and context in the most efficient way possible.

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 format is covered. However, the description does not specify what 'active' means, whether results are paginated, or that the operation is read-only. For a simple list tool with no annotations, more context would be helpful, but the core requirements (project_id) are met.

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. It mentions 'for a project', which clarifies that project_id is the project identifier, but it does not explain the expected format or any constraints. The description adds a little meaning but not sufficient detail given zero schema descriptions.

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 states a specific verb ('List'), a resource ('workspaces'), and a qualifier ('active' and 'for a project'). This clearly distinguishes it from siblings like get_workspace (single) and create_workspace/delete_workspace (write operations). It leaves no ambiguity about what the tool does.

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 the tool is for enumerating workspaces of a given project, but it does not explicitly contrast with get_workspace (single) or explain when to prefer this over other listing tools. Context is clear but not explicit; no alternatives or exclusions are mentioned.

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