get_workspace_members

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

With no annotations provided, the description carries full burden and does well: it explains filter semantics (case-insensitive contains, exact role_slug, AND combination), order_by prefix behavior, paginated envelope structure, and self-hosted specific behavior (all members in one page). This goes beyond typical list-tool descriptions, though minor aspects like authentication or workspace context are not addressed.

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 concise and well-structured, with a one-sentence purpose, a filters paragraph, and labeled 'Args:' and 'Returns:' sections. It is front-loaded with the core function, and every sentence provides distinct value without 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?

Despite the output schema, the description enriches understanding by covering all parameters, return fields (including role, role_slug, is_active, is_bot), pagination envelope, and the self-hosted single-page behavior. It is comprehensive for a listing tool, with only minor ambiguity about how 'current workspace' is resolved.

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 schema has 0% coverage for parameter descriptions, but the tool description explicitly covers every parameter: first_name/last_name/email/display_name as case-insensitive contains, role_slug as exact, is_active and is_bot with implied boolean filtering, and order_by with prefix '-' for descending. This adds substantial meaning beyond the bare schema.

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 opens with 'List members of the current workspace (filterable)', using a specific verb+resource that clearly distinguishes it from sibling tools like get_project_members. The mention of filters further clarifies its purpose.

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 'current workspace' phrasing provides clear context, but the description does not explicitly state when to use this tool versus alternatives like get_project_members. No exclusions or alternative references are given, leaving the when-to-use guidance to be inferred from the tool name.

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