weeek_list_workspace_members

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

With no annotations, the description fully discloses behavior: it is a read operation (lists members), enforces pagination (default 20, max 50), and returns shaped members. It does not contradict any safety hints because none are provided.

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 but thorough, with no wasted words. Each sentence serves a purpose: purpose, usage guidance, return shape, pagination, and token determination. The most critical information is front-loaded.

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?

Given no output schema, the description provides return shape, pagination details, and when to use. It covers all necessary context for an agent to correctly invoke this tool.

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?

Input schema already covers both parameters (limit, offset) with descriptions. The description adds value by explaining the default limit protects against the 25k-token response cap, which is not in the 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 clearly states the tool lists workspace members with specific return fields (id, name, email, role). It distinguishes from siblings by stating it is needed for resolving names to IDs before using other tools.

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 description explicitly says 'Use this FIRST when an agent needs to resolve a person's name to a user ID' and lists specific sibling tools (weeek_list_tasks, weeek_create_task, weeek_update_task) that require the output. It also notes workspace is determined by API token.

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