List workspace members

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds the API endpoint and confirms it is a retrieval, but does not discuss pagination, rate limits, or authorization beyond what is implicit. Acceptable given annotations cover safety.

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?

Two sentences: one states the action, the other provides the API call. No extraneous information, front-loaded with the key purpose. Every sentence earns its place.

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 simple list operation with one parameter and no output schema, the description adequately covers what the tool does and how (API call). Could mention the return type (array of users) but not required. Overall, complete enough.

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?

There is one parameter, ownerId, fully documented in the schema with description 'The ID of the team'. The tool description does not add additional meaning beyond referencing 'the provided ID'. With 100% schema coverage, 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 clearly states it 'Lists workspace members' and 'Retrieves the list of users', with a specific verb (list/retrieve) and resource (workspace members). This distinctively separates it from siblings like render_remove_workspace_member or render_list_owners.

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 for reading workspace members. While it doesn't explicitly state when not to use, the context is clear and the sibling list provides differentiation. No alternative tools are named, but the purpose is straightforward.

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