remove_space_members

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

The description explains key behaviors beyond annotations: idempotent removal, member resolution (UUID/email/name), and replacement of the full members array. This adds context to the idempotentHint annotation and clarifies the mutation pattern.

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?

Two sentences with no wasted words. The first sentence states purpose and idempotency; the second explains member resolution and effect. Information is front-loaded and easy to parse.

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 description covers the core operation and member resolution but lacks context about prerequisites (e.g., space existence, permissions) and does not differentiate from similar sibling tools like 'remove_space_role_members'. Given the presence of an output schema, return values need not be explained.

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?

While schema descriptions are generic (e.g., 'string that will be trimmed'), the tool description adds meaning for 'members' (accepts UUID/email/name, resolves to UUIDs, replaces full array). This compensates for the schema's lack of detail. However, 'space', 'class', and 'type' remain under-described.

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 action ('remove members') and the resource ('existing Huly space'), with the specific verb 'remove' distinguishing it from sibling tools like 'add_space_members'. It also mentions idempotency, adding precision.

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?

No explicit guidance on when to use this tool versus alternatives such as 'remove_space_role_members' or 'remove_channel_members'. The description does not mention prerequisites, limitations, or when not to use it.

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