list_workspaces

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

No annotations are provided, so the description carries the full burden. It mentions 'authenticated user' (implying auth needs) and 'content counts' (hinting at output behavior), but lacks details on rate limits, pagination, error handling, or what 'content counts' entail. For a list operation with zero annotation coverage, this is insufficient.

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 that front-loads the core purpose ('List all workspaces') and adds key details ('authenticated user', 'content counts') without waste. Every word earns its place, making it easy to parse.

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 no annotations, no output schema, and a simple input schema, the description covers the basic purpose and hints at authentication and output content. However, it lacks details on behavioral traits (e.g., pagination, errors) and doesn't fully compensate for the missing structured data, making it adequate but with gaps.

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 100%, so the schema fully documents the 'includeStats' parameter. The description adds no additional parameter information beyond what's in the schema, but it does imply the parameter's effect by mentioning 'content counts'. Baseline 3 is appropriate as the schema handles the heavy lifting.

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 verb ('List') and resource ('workspaces'), specifying 'all workspaces for the authenticated user with content counts'. It distinguishes from siblings like 'get_workspace' (single workspace) and 'get_workspace_stats' (statistics only), though it doesn't explicitly name alternatives. The purpose is specific and actionable.

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 by mentioning 'authenticated user', suggesting it requires authentication, but doesn't explicitly state when to use this tool versus alternatives like 'get_default_workspace' or 'get_workspace_by_name'. No exclusions or clear context for choosing this over other workspace-related tools are provided.

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