sw_delete_friend

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

The description goes well beyond the destructiveHint annotation by disclosing the dry-run preview behavior and the fact that no network call occurs without confirm:true. This is critical safety context that the annotation alone does not convey, making the tool's behavior highly transparent.

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 well-structured sentence that front-loads the primary action and then efficiently explains the safety mechanism. Every word earns its place, with no redundancy or filler.

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 delete tool with no output schema, the description covers the operation, the confirm safety switch, and the network-call behavior. It could optionally mention the preview's content or permanent nature, but the destructiveHint annotation and the clear 'removes the friendship' statement provide adequate context.

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 input schema already provides complete descriptions for both parameters (id and confirm) at 100% coverage. The description restates the confirm semantics but does not add additional meaning beyond what the schema already offers. Therefore, a baseline score of 3 is appropriate.

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 precisely what the tool does: 'Remove a Splitwise friendship by user id.' It uses a specific verb (Remove) and resource (Splitwise friendship), clearly distinguishing it from sibling tools like sw_list_friends and sw_create_friend. The added confirm behavior further reinforces the tool's core purpose.

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 clearly implies this is the tool to use for deleting a friendship and explicitly explains the two modes of use (dry-run without confirm:true, actual deletion with confirm:true). However, it does not name sibling alternatives or state exclusions, so it slightly falls short of full usage guidance.

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