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

Annotations already carry destructiveHint=true, readOnlyHint=false and idempotentHint=false, so safety is covered structurally. The description still earns credit because it spells out exactly what is destroyed: 'all agents except the one passed in params will be removed' — that specific consequence is not derivable from the hints alone. It stops short of confirming whether the call is atomic or what happens if the ID is invalid.

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, and the consequence (who gets removed) is placed immediately after the operation statement. The first sentence merely restates the tool title, which is the only wasted 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 two-parameter mutation tool whose annotations already declare destructive/non-idempotent behavior, the description supplies the one thing an agent most needs — the replace-all semantics. Error behavior and required permissions are absent, but with no output schema and full param coverage the gap is minor.

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% (inbox_id and user_ids are both documented in the schema), so the baseline of 3 applies. The description references the parameter only obliquely as 'the one passed in params', which is singular while user_ids is an array of integers — a mild inconsistency that adds ambiguity rather than clarity.

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 second sentence makes the operation's real semantics explicit: this is a replace-style update that deletes every existing agent except the passed ID(s), which is far more informative than the bare title. It is clear as a verb+resource, but it never names the sibling operations it competes with (add_inbox_member, remove_inbox_member, update_agents_in_team), so an agent must infer the distinction.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as add_inbox_member or remove_inbox_member, which are the obvious non-destructive ways to change inbox membership. The destructive-replace nature is stated but never framed as a selection criterion.

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