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 only states the action without disclosing any behavioral traits such as read-only safety, required authentication, potential pagination, or the structure of the returned list. While a simple list operation implies no side effects, this is not explicitly conveyed, leaving some ambiguity.

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 with no redundant information. It is appropriately front-loaded and every word adds value.

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 there are no parameters, no output schema, and no annotations, the description provides a complete enough overview for a simple list operation. It does not specify the return format or any caveats, but the core functionality is clearly conveyed. A small improvement would be mentioning the return structure, but it is not necessary for such a trivial tool.

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 there is nothing for the description to add. Per the baseline for 0 params, a score of 4 is appropriate, as the schema already fully covers the (empty) parameter space.

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') and resource ('workspaces'), clearly indicating the tool's function. It distinguishes from sibling tools (start_tracking, stop_tracking, show_current_time_entry) which are all time-tracking operations, making this the obvious choice for workspace enumeration.

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 when one needs to see available workspaces, but it does not explicitly state when to use this tool versus siblings. There is no mention of alternatives or exclusions, but the purpose is straightforward enough that it is easy to infer.

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