Delete Friend

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds a meaningful non-effect ('Does not affect shared expenses or balances'), which is useful context for a destructive operation. However, it does not mention reversibility, permissions, or any cascading effects beyond the relationship 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 two short sentences with no filler. The core action is front-loaded, and the important caveat about expenses and balances is stated directly.

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 one-parameter delete operation with an output schema, the description is largely complete: it states the action and a key non-obvious side-effect. It could add more about the semantics of friend_id, but the tool is simple enough that an agent can infer 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?

Schema description coverage is 0%, so the description should compensate by explaining what friend_id means and how it is used. It does not mention the parameter at all, though the property name 'friend_id' and the phrase 'Remove a friendship' provide some implicit meaning.

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 uses a specific verb ('Remove') and a specific resource ('a friendship'), making the tool's purpose immediately clear. The phrasing also distinguishes it from sibling tools like delete_group by targeting the friendship relationship rather than a group.

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 no explicit guidance on when to use this tool versus alternatives such as remove_user_from_group or create_friend. The purpose is implied by the name and first sentence, but there is no stated condition, exclusion, or alternative.

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