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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds the concrete consequence that earns its place: all agents not in the supplied list are removed. That is the specific blast radius an agent needs before calling, and it goes meaningfully beyond the boolean hint. It stops short of stating auth requirements or what happens with an empty list.

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 padding, and the destructive consequence is front-loaded after the name echo. But the entire first sentence is a restatement of the title and earns nothing, so the content-to-length ratio is only adequate rather than tight.

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 description covers the critical roster-replacement behavior, but omits edge cases an agent would want: whether an empty user_ids clears the team, whether omitted users are warned about, and what the call returns. Adequate for the happy path, incomplete for the destructive path.

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, but the description actually corrects the schema: user_ids is described there as 'users to be added,' whereas the description makes clear the call is a full replacement and prior members are dropped. That reframing is real added meaning, though the singular 'the one passed in params' conflicts with the array type and costs it the top score.

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 name verbatim, so the real signal is the second sentence, which does convey the key semantic that this is a replace-the-roster operation rather than an append. However, it says 'the one passed in params' while the parameter is an array (user_ids), which muddles exactly what the tool does, and it never distinguishes itself from siblings like add_team_member, remove_team_member, or update_agents_in_inbox.

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 explicit when-to-use guidance and no named alternative. An agent must infer from the destructive wording alone that this is the bulk-replacement tool rather than the incremental add_team_member/remove_team_member pair, which is exactly the kind of routing decision the description should make for it.

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