workspace_members

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

No annotations are provided, so the description must carry the behavioral burden. The auditing/permission-review framing implies a read-only lookup, but it says nothing about pagination, result volume, or whether rate limits apply to large workspaces.

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?

One front-loaded sentence with no filler, leading with the usage trigger. Slightly ambiguous phrasing ('before assignment' of what) keeps it from a perfect score.

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?

A simple read tool with fully documented parameters and no output schema; the description is adequate but omits any sense of return shape, ordering, or size, which matters for workspace member listings that can be large.

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 description coverage is 100%, with well-documented fields, filter enum, and workspaceId, so the params are already self-explanatory. The description adds no further meaning beyond the 'known workspace' hint toward workspaceId, which matches the baseline of 3.

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 makes clear this returns members of a specific Trello workspace, and 'known Trello workspace' implicitly distinguishes it from the global search_members sibling. The verb 'list'/'retrieve' is never stated outright, but the resource and scope are unambiguous.

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 concrete when-to-use contexts: before assignment, auditing, and permission review. The 'known workspace' qualifier implies the workspaceId must already be in hand, steering agents away from this tool when searching across workspaces, though no alternative is named explicitly.

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