manage_group_members

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

Annotations already indicate destructiveHint=true, but the description adds crucial behavioral details: that removal is destructive, requires confirmation unless confirm=true, and that adding executes immediately. It also explains that first_name/last_name can be used for new invites or disambiguation. This goes beyond the annotation's bare hint, providing practical operational transparency.

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 tight and well-organized. The primary action is stated first, followed by identification schemes and behavior nuances. Every sentence adds value without redundancy or fluff, making it easy for an agent to parse quickly.

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 complexity (8 parameters, dual actions, destructive behavior) and the existence of an output schema, the description is essentially complete. It covers identification, add/remove behavior, confirmation, and invite specifics. It could mention response or error handling, but with an output schema present, that is not required. Overall, it provides enough context for correct invocation.

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?

With schema description coverage at 0%, the description carries the full burden of explaining parameters. It does so well: it explains how to specify the group (group_id or group_name) and member (user_id or email), the role of first_name/last_name, and the confirm parameter's function. The action parameter is self-explanatory via the enum. Some nuances (e.g., behavior when both group_id and group_name are provided) are not addressed, but the core semantics are well-covered.

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 tool's purpose: 'Add or remove a member of a Splitwise group.' It names the specific verb and resource (group member management) and is readily distinguishable from sibling tools like create_group or delete_group, which handle group-level operations.

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 explains how to identify the group and member (via group_id/group_name and user_id/email), and clarifies the difference between add and remove, including the confirm flag for removal. It does not explicitly name alternative tools, but the guidance for when to use add vs. remove is clear and sufficient for an agent to select this tool appropriately.

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