List Weeek workspace members

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds useful context beyond this: output fields ({id, email, firstName, lastName}) and that member id is a string 'unlike most Weeek resources,' which is non-obvious and behaviorally relevant. No contradiction.

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?

Three sentences, each earning its place: primary purpose plus output structure, sibling distinction, and a concrete use case with ID type note. No redundancy, front-loaded with the most important information.

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, read-only list operation with comprehensive annotations and an output schema, the description covers what an agent needs: scope (all workspace participants), distinguishing from the self endpoint, and the string-typed member id. Complete.

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?

Tool has zero parameters, so baseline is 4. The description adds no parameter-specific meaning, but none is needed; it focuses on output and usage, which is appropriate for a parameterless endpoint.

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?

States it is the 'PRIMARY tool for member discovery' and 'returns every member of the configured Weeek workspace' with specific fields. Explicitly distinguishes from weeek_get_me, which returns the caller. Clear verb+resource with sibling differentiation.

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?

Provides explicit use case: 'Use when an agent needs to resolve a name/email to a member id.' Explicitly names weeek_get_me as a distinct alternative and explains the difference ('returns the caller' vs 'every workspace participant'). Clear when/when-not guidance.

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