get_workspace_members

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

Annotations already indicate read-only, non-destructive, and open-world behavior. The description adds that it returns user IDs, which is useful, but does not disclose additional behavioral details such as pagination, output format, or performance implications. With annotations present, this is adequate but not exceptional.

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?

The description is exactly two sentences: the first states what the tool does, the second provides a practical use case. It is direct, front-loaded, and contains no filler or redundancy.

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-only lookup tool, the description fully covers its purpose, output content, and common usage scenario. No output schema exists, but the description sufficiently specifies the key return element (user IDs). It is complete for its intended purpose.

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, so no parameter explanation is needed. The schema coverage is trivially 100%, and the description's 'all workspace members' clarifies the implied full scope, which is consistent with the empty parameter list.

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 the tool's function with a specific verb and resource: 'Get all workspace members with their user IDs.' It distinguishes from sibling tools like get_project_members by specifying 'workspace' scope, making it immediately clear what is returned.

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 gives explicit usage context: 'Call this to find assignee IDs before creating or filtering work items by assignee.' This clearly indicates when to use the tool, though it does not explicitly mention when not to use it or name alternatives like get_project_members.

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