kaiten_list_space_users

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

With no annotations, the description carries the full burden for behavioral disclosure. It only says 'List users' and does not mention pagination, response shape, ordering, permission requirements, or the impact of the compact flag. The read-only nature is implied by 'List' rather than stated.

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 a single, front-loaded sentence with no filler or redundancy. It earns its place and is appropriately sized for a simple list operation.

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?

The tool is simple and the schema covers its two parameters, so the minimal description is workable. However, with no annotations and no output schema, the description does not explain what the returned user list looks like, whether results are paginated, or how this list differs from kaiten_list_users. It is minimally viable but leaves gaps.

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%, so the schema already documents both parameters. The description itself adds no parameter meaning, but it does not need to; the compact parameter has a clear schema description about avoiding heavy fields, and space_id is defined as 'Space ID'.

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 states a specific verb ('List') and a specific resource ('users of a Kaiten space'), with the required space_id reinforcing the scope. It is clear enough for an agent to understand the primary function, though it does not explicitly contrast with similar sibling tools like kaiten_list_users or kaiten_list_group_users.

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 gives no guidance on when to use this tool versus kaiten_list_users, kaiten_list_group_users, or kaiten_list_sd_users. The phrase 'of a Kaiten space' implies a scoping condition, but no exclusions or alternative routing are provided.

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