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

The description adds substantial behavior beyond annotations: additive single-member scope, authorization roles, invitation/notification side effects, and no-op behavior with already_member:true. It does not explain the annotation's destructiveHint:true or clarify what, if anything, is overwritten on a role change.

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?

The description is dense but front-loaded and efficient. Every clause carries information about scope, authorization, side effects, or idempotent behavior, with no filler.

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 mutation tool with no output schema and only partial schema coverage, the description covers the critical operational context: single-member scope, authorization, idempotency, and notification/no-op outcomes. The main gap is parameter-level detail, especially for strengths and the optional acting-agent field.

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 only 40%, so the description must compensate, but it barely explains parameters. It touches on role changes and the acting agent, yet gives no semantics for team_id, agent_id, or strengths beyond what the schema already shows.

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 states a specific verb and resource: add/update ONE team member. It also distinguishes the scope from set_team_roster by saying it leaves all other members untouched, so an agent can separate it from the roster-setting sibling.

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?

It names the alternative set_team_roster and gives clear authorization and outcome conditions: new/role-changed versus same role. The when-to-use guidance is strong, though it does not explicitly say when not to use this tool beyond the roster distinction.

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