list_members

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

With no annotations, the description carries the transparency burden. It clearly identifies the operation as a list (read-only) and specifies output contents, and the UUID usage hint adds context. However, it does not explicitly state that it returns all members, whether pagination applies, or if any authorization is required, so some behavioral details are left implicit.

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 short sentences, front-loaded with the core action and immediately followed by actionable guidance. Every word 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 zero-parameter list with an output schema, the description is nearly complete: it states what is returned and why. A minor gap is not explicitly saying it returns all workspace members or contrasting with find_member, but these are not essential for correct invocation.

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 and schema coverage is 100%, so the description has no parameter semantics to add. Baseline 4 applies; the description correctly focuses on output usage instead.

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?

Description opens with a specific verb and resource: 'List workspace members', then enumerates the returned fields (UUIDs, emails, display names). It also states the intended downstream use of the returned UUID, making the tool's role unambiguous and distinct from sibling find_member.

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 second sentence gives concrete guidance: use the returned member UUID for fields like assignees, owned_by, and lead. This establishes when the tool is useful, though it does not explicitly compare with find_member or state exclusions.

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