Remove Space Member

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds two useful pieces of context beyond annotations: it "changes community state" and requires confirm=true, which the annotations do not mention. It still doesn't say whether removal is permanent or reversible.

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 short sentences with no filler, and the behavioral constraint is front-loaded. The only waste is the opening restatement of the title, which occupies half the text.

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 destructive, non-idempotent mutation with no output schema, the annotations carry most of the safety burden and the schema fully documents parameters. The description adequately flags state change and the confirm gate, but leaves open what happens to the removed member's data or whether the action can be undone.

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 baseline is 3. The description reinforces the confirm parameter's intent, but adds no syntax, format, or constraint details beyond what the schema already documents for email, account, confirm, and 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 first sentence restates the tool title verbatim ("Remove Space Member"), adding essentially nothing over the name. The resource is unambiguous, but the description never distinguishes this from close siblings such as remove_member, delete_community_member, or delete_space_group_member.

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 only hints at when to set confirm=true ("for the user-requested action"). It gives no guidance on when to use this tool versus add_space_member, remove_member, or other member-removal siblings, and no prerequisites are stated.

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