unassign_conversation

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Remove') but does not disclose side effects, permissions, idempotency, reversibility, or what happens if the member is not assigned. For a mutation tool, this is a significant gap.

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, front-loaded sentence with no filler or redundant information. Every word contributes to the meaning, making it highly efficient.

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 has 3 parameters, no annotations, and no parameter descriptions, the description is incomplete. It does not provide context on when to use the tool, what the response will be, or any edge-case behavior. The description does not adequately round out the tool's semantics.

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 description coverage is 0%, so the description must compensate. It does not mention 'api_token' at all, and only implicitly references 'member' and 'conversation' without mapping them to the actual parameters 'member_id' and 'conversation_id'. The description adds minimal semantic value over the schema.

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 'Remove a member assignment from a conversation' uses a specific verb ('Remove') and clearly identifies the resource ('member assignment') and the object ('conversation'). It distinguishes itself from the sibling tool 'assign_conversation' by indicating the opposite action.

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 implies usage (when you need to unassign a member), but it does not explicitly mention when to use this tool over alternatives or provide exclusions. There is no mention of prerequisites or comparisons with sibling tools like 'assign_conversation'.

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