remove_contact_from_segment

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

With no annotations, the description must carry behavioral disclosure. It explicitly reveals the destructive HTTP method (DELETE), which signals mutation, but it does not disclose idempotency, behavior when the membership does not exist, permissions, or response semantics.

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?

A single front-loaded sentence conveys the action, resource, and HTTP method without redundancy. Every element earns its place.

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 two-parameter removal operation with fully documented parameters, the description is largely complete. Minor omissions around side effects and response behavior prevent a 5, but an agent can likely invoke this tool correctly based on the provided text.

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 100%, with both parameters already documented as 'The contact id' and 'The segment id.' The description adds no extra parameter meaning beyond the endpoint path, so baseline 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 a specific action ('Remove'), a specific resource ('contact from a segment'), and the exact HTTP endpoint. This clearly differentiates it from sibling tools like add_contact_to_segment and list_contact_segments.

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 verb 'Remove' and endpoint pattern imply this tool is for severing a contact-segment membership, but the description does not explicitly state when to prefer it over alternatives or what conditions apply. Sibling tools exist for adding or listing segment memberships, but no routing guidance is given.

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