fmod_remove_relationship

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

No annotations are provided, and the description only states 'remove' without detailing behavioral traits such as whether removal is permanent, what happens if the relationship does not exist, or any side effects. The user must infer behavior from the brief code-like representation.

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 extremely concise, consisting of one sentence plus a code-like representation. It conveys the essential meaning without any redundant information.

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?

The description covers the core purpose but lacks details on return values, error handling, or examples. Given the tool has three required parameters and no output schema, additional context would be helpful, but the description is not severely incomplete.

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 description adds a code representation that clarifies the meaning of the 'target.relationships[name].remove(other)' pattern, which helps understand the role of 'relationship' as a name. However, it does not elaborate beyond the schema descriptions, and the 'relationship' parameter lacks a description in the schema, but the tool description partially compensates.

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 explicitly states the action ('Remove an object'), the resource ('one of a target's relationships'), and provides a code representation that clarifies the syntax. It also clearly distinguishes from the sibling tool fmod_add_relationship.

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 does not provide any guidance on when to use this tool versus alternatives like fmod_add_relationship. No context on prerequisites, failure conditions, or typical use cases.

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