List Space Users

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

Annotations already declare this as read-only, idempotent, and non-destructive, so the description doesn't need to repeat that. It does add that the output is membership data for a space, but it doesn't disclose response shape, pagination, or whether the list includes all members in any particular state.

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 compact and efficient. It front-loads the core purpose, then immediately gives the actionable use case and the source for the required parameter, with no wasted words.

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 simple read-only list operation, the description is sufficient: it explains what the tool returns, why to use it, and how to obtain the required spaceId. The main gap is that it doesn't describe the response shape or verbosity behavior, but those details are partially covered by the schema and are not critical for a correct call.

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%, covering both spaceId and verbosity. The description adds the practical purpose of finding user IDs, but it doesn't substantially enrich parameter meaning beyond what the schema already provides.

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 identifies a specific resource (members of a space) and a concrete use case (finding user IDs to populate ownerId on card creation/update). It is clear enough, though it doesn't explicitly contrast with the similar kaiten_list_users sibling.

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 clearly states when to use this tool: when the target user isn't the API caller and an ownerId is needed. It also tells the agent where to get the spaceId (kaiten_list_spaces), but it doesn't mention exclusions or when an alternative like kaiten_list_users would be preferable.

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