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

With no annotations, the description carries the full burden, and it does disclose the access scope ('each team workspace they're in' — not all workspaces) and the returned fields. It never states it is a read-only, side-effect-free operation or whether result size is bounded, which is the main remaining gap for a zero-annotation tool.

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: what it returns, how siblings consume the result, and the selection rule. Front-loaded with the resource definition and no repeated or filler text.

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 parameterless read tool with no output schema, the description supplies return shape, access scope, and the tie-in to sibling tools' `workspace` argument. Absent an explicit read-only statement and any hint about ordering or a default personal entry, it is nearly complete but not airtight.

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 takes no parameters, so baseline is 4; the schema is empty rather than misleading. The description usefully explains the `workspace` argument that sibling tools accept, which aids correct orchestration even though it is not a parameter of this tool.

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 names the resource ('the user's workspaces') and enumerates exactly what each entry contains (name, id, their role), which is effectively a listing verb plus scope. It distinguishes itself from siblings like list_members or list_collections by making clear these are workspaces the user belongs to, though it never uses an explicit verb like 'list'.

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?

It explicitly frames the downstream use case: notes/tasks/collections tools take a `workspace`, and without one they fall back to the personal workspace, plus a decision rule ('Pick a team when the user names it or the work is the team's'). That is clear contextual guidance, but it stops short of an explicit 'call this tool when X, not Y' trigger for the tool itself.

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