list_workspaces

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

No annotations, but the description discloses the backing store (workspaces.toml), the payload shape (names + descriptions), and an important security trait ("Tokens are never returned"). It stops short of explicitly stating that the call is read-only or has no side effects, but 'list' plus the omission of tokens makes the safety profile clear enough.

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?

Three short sentences, with purpose and the return fields front-loaded and the routing guidance immediately after. No filler, and every sentence carries information the schema does not.

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 values need no explanation, and a zero-param tool has no parameter gaps to fill. The description covers purpose, discovery role, and a security caveat, which is everything needed to call it correctly.

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 schema has zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly adds that the output contains names and descriptions rather than any parameter detail.

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?

States a specific verb and resource ("List the Slack workspaces") plus the source and the returned fields (names + descriptions). This is clearly distinguishable from every sibling, all of which operate inside a single workspace.

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?

"Call this first to discover the `workspace` values accepted by every other tool" gives an explicit when-to-use and explains the ordering relationship to all sibling tools. It also implicitly excludes other uses, so the agent does not have to infer routing.

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