aap_remove_user_from_team

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

Annotations indicate readOnlyHint=false and destructiveHint=false, but the description adds no behavioral context beyond the basic action. It does not mention idempotency, error behavior if the user is not on the team, required permissions, or any side effects, so it adds little beyond the annotations and the action itself.

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 concise and follows a clear Args/Returns structure. It includes all essential information without redundancy, though the nested params block is slightly awkward and repeats schema field names.

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 tool's simplicity, the description covers the core operation, parameters, and return value. It lacks usage guidance and edge-case behavior, but the annotations and output schema provide additional context. This is adequate for a straightforward removal tool but not fully comprehensive.

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?

The schema has 0% description coverage, so the description's parameter list is important. It provides basic meanings for team_id ('Team ID') and user_id ('User ID to remove'), which slightly extends the schema titles. However, it does not add details about constraints, relationships, or expected values beyond what the field names imply.

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 clearly states the specific action ('Remove a user from an AAP team') and resource, distinguishing it from siblings like aap_add_user_to_team and aap_remove_host_from_group. The verb is explicit and unambiguous.

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 no guidance on when to use this tool versus alternatives, nor does it mention that it is the counterpart to aap_add_user_to_team or any prerequisites for removing a user from a team. It simply describes the operation without contextual usage direction.

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