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. The phrase 'All workspaces' implies a read-only listing, but it does not disclose any other behavioral traits such as pagination, filtering, authentication requirements, or what 'plan_capabilities' actually entails. This is minimal and lacks depth.

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 extremely short, which is concise, but it is a fragment and not a well-structured sentence. It communicates a minimal idea but sacrifices clarity and structure, making it less effective than a concise but complete sentence.

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?

For a list tool with no annotations and no output schema, the description is insufficient. It does not describe return format, pagination, or the meaning of 'plan_capabilities'. Given the many sibling tools, it should provide more context about what makes this listing unique or how it relates to other workspace tools.

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 tool has zero parameters, so the description does not need to explain parameter meanings. According to the baseline for 0 params, the score is 4. The description adds no parameter information, but none is needed.

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 'All workspaces with plan_capabilities' is a noun phrase rather than a sentence with a verb, so it does not explicitly state the action. The tool name 'list_workspaces' implies listing, and the description adds the detail about plan_capabilities, but it does not clearly distinguish from sibling tools like get_workspace beyond the plural form.

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 such as get_workspace or get_info. There is no mention of appropriate contexts, comparisons, or exclusions.

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