sw_remove_user_from_group

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

The annotation only states destructiveHint=true, but the description goes further by disclosing the dry-run behavior, the no-network-call guarantee without confirm, and the requirement for confirm to actually remove. This adds substantial behavioral context beyond the annotation.

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?

Two sentences: first states the core action, second explains the confirm behavior. No fluff, front-loaded with purpose, and every word earns its place.

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 destructive tool with no output schema, the description covers the critical behavior (dry-run vs actual removal) that an agent must know. It doesn't describe the preview contents, but that's a minor gap. Overall, it's complete enough given the simplicity of the operation.

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 already documents all three parameters with 100% coverage. The description repeats the confirm behavior that the schema also mentions, but does not add extra meaning for group_id or user_id. Baseline of 3 is appropriate since 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 clearly states the action: 'Remove a user from a Splitwise group.' This is a specific verb+resource pair that distinguishes it from sibling tools like sw_add_user_to_group and sw_delete_group. The dry-run/confirm distinction is also included.

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 gives guidance on when to use confirm:true vs false, which is essential for safe usage. It does not explicitly mention alternatives, but the tool's name and purpose make it clear when to use it relative to siblings. The safety guidance is valuable and partially addresses usage.

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