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

The annotations already declare destructiveHint=true and idempotentHint=true, so the description is not responsible for the core safety profile. It adds useful behavioral context by stating the personal-API-key requirement and the organization-key restriction. It does not describe the escalation-policy refusal behavior, but that detail is covered in the parameter schema rather than needed here.

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 two tightly written sentences with no wasted words. The core operation is front-loaded, followed by the important authentication restriction. It is appropriately sized for a tool whose parameters are fully documented in the schema.

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?

Given the destructive nature of the operation, rich annotations, full schema description coverage, and no output schema, the description is largely complete. It clearly states the replacement behavior and the key authentication constraint. It could add one line about the escalation-policy refusal covered by the force parameter, but that is already fully explained in the schema.

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 all three parameters are already documented in the input schema, including the meaning of force and membership_ids. The description adds only the high-level notion of replacing the manual list and does not add syntax or edge-case guidance beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 gives a specific verb and resource: 'Replace a team's manual member list.' This clearly distinguishes the operation as a bulk replacement of manual team membership rather than an individual member update. It does not explicitly name or differentiate from close siblings such as update_member or remove_member, so it falls short of the top score.

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 provides one important usage constraint: a personal API key is required, and organization keys cannot manage teams. However, it does not explain when to choose this bulk-replace tool over alternatives like update_member or remove_member, leaving the agent to infer that from the operation name.

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