Remove team account

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds important behavioral context beyond annotations: the account is not deleted but reassigned to the default team, which materially affects how an agent should reason about the operation's side effects.

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 a single, front-loaded sentence with no filler. Every phrase contributes either the core action or the key behavioral consequence.

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 simple two-parameter mutation tool whose annotations already cover destructiveness and openness, the description gives the critical outcome: reassignment rather than deletion. It leaves parameter semantics undocumented, but the required identifiers are self-evident and no output schema exists that needs explaining.

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?

There are two required parameters, teamId and accountId, with 0% schema description coverage. The description implies that the parameters identify a team and an account, but it provides no additional meaning, format, or constraint beyond that implication.

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: 'Remove an account from a team.' It also distinguishes the action from deleting an account by clarifying reassignment to the default team, and it is clearly differentiable from sibling tools like add_team_account and delete_team.

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?

Usage is implied by the action: use it to remove an account from a specific team. However, the description does not explicitly state when to use this versus alternatives such as add_team_account, update_team, or delete_team, nor does it mention prerequisites or exclusions.

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