Contract Testing: Admin Patch Team Users

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

Annotations already signal a non-read-only mutation, and the description adds the JSON Patch mechanism and admin-level scope, which provides some behavioral context. However, it does not disclose consequences like partial application, duplicate removals, required permissions, or response behavior.

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 short, front-loaded with the core action, and easy to scan. The 'Parameters' section duplicates schema content unnecessarily, but overall the structure is efficient and readable.

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?

The schema covers the parameter constraints well, and annotations cover the basic safety profile. Still, the description omits when to use this over closely related admin team-user tools and does not describe the response or edge-case behavior, leaving noticeable gaps for an admin mutation.

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 schema fully documents both teamId and operations. The description repeats the parameter names and descriptions without adding meaning beyond the schema, so it meets the baseline but does not go further.

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 uses a specific verb and resource: 'Add or remove individual users from a team using JSON Patch.' The phrase 'individual users' plus 'JSON Patch' distinguishes it from sibling tools like admin_set_team_users or admin_remove_user_from_team, and the admin qualifier clarifies scope.

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 states what the tool does but gives no guidance on when to prefer it over alternatives such as contract-testing_admin_set_team_users or contract-testing_admin_remove_user_from_team. There is no explicit 'use this when' or exclusionary context.

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