get_workspace_members

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It doesn't reveal whether this returns paginated results, the return format, behavior with invalid team_id, authentication requirements, or whether guests/inactive members are included. For a read tool with zero annotation coverage, this is minimal.

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?

A single efficient sentence with zero waste. It front-loads the verb and resource clearly. Could arguably be judged under-specified rather than concise, but the text it does contain is well-formed and direct.

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?

This is a simple read-listing tool with one parameter and no output schema. The description names the purpose and parameter is covered by schema. However, with no annotations and no behavioral context (pagination, return shape, filtering), it falls short of complete for a list-type tool. Baseline information is present but nothing more.

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 coverage is 100% with a single parameter (team_id, 'The workspace/team ID'). The description doesn't add semantics about what the ID format is or where to obtain it, but the schema adequately documents the only parameter, so the baseline of 3 is appropriate.

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 'Get all members of a workspace' uses a specific verb (get) and resource (workspace members), clearly stating the scope ('all'). It distinguishes from siblings like get_task_members, get_list_members, and get_space_members, which target different resource types, though it doesn't explicitly name the alternative.

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?

No guidance is given on when to use this vs related tools like get_space_members, get_task_members, or get_list_members. The distinction between workspace, space, list, and task membership is implied but never stated. No exclusions, prerequisites, or context about when this tool is appropriate.

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