Remove a Niche from Spaces

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

Goes well beyond the destructiveHint annotation: discloses the authorization model (org owner or team admin, else 403 INSUFFICIENT_ROLE), the all-or-nothing transaction semantics, error payload contents (offending ids), idempotency of already-removed ids, zero cost, and a 2-calls-per-minute-per-niche limit. This is exactly the context an agent needs before invoking a destructive tool.

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?

Front-loads the action and the access implication, then layers error behavior, idempotency, and rate limiting. Dense but nearly every clause carries operational value; slightly long for a two-parameter tool, though not padded.

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?

With no output schema, the description supplies the return keys (`removed`, `notPresent`), the success/failure modes, auth requirements, and rate limits. Nothing an agent needs in order to call this mutation correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real semantics: `spaceIds` controls visibility/access, ids come from `list_spaces`, and every id should be packed into a single call. It doesn't explain the uniqueness/1-100 bounds the schema already covers, which is fine.

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?

States a precise verb and resource ('take a niche out of one or more Spaces') and immediately contrasts with its inverse sibling `add_niche_spaces`. An agent can distinguish it from `remove_niche_labels` and `add_niche_spaces` without opening any schema.

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?

Explicitly names the undo path (`add_niche_spaces`), tells the agent to batch all ids into one call due to the per-niche rate limit, and instructs the agent to relay a 403 to the user rather than retry. Both when-to-use and when-not-to-use conditions are spelled out.

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