remove_contact_from_segment

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

The description does not add behavioral context beyond what annotations already provide. Annotations indicate destructiveHint=true and idempotentHint=true, but the description omits any mention of side effects (e.g., the contact remains in other segments or that this action is reversible).

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 at one sentence, with no wasted words. However, it is overly brief and lacks important context, balancing efficiency with incomplete 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 lacks completeness given the tool's mutation nature and the absence of an output schema. It does not explain what happens after removal (e.g., the contact is not deleted from the system), nor does it address reversibility or relationships with other entities. Annotations partially compensate, but the description should provide more 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 covers both parameters (id, segment_id) with descriptions, achieving 100% coverage. The description adds no additional meaning beyond the schema, so it meets the baseline but does not enhance understanding.

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 contact from a segment' clearly states the verb (remove) and the resources (contact, segment). It distinguishes from the sibling tool 'add_contact_to_segment', which performs the opposite action. However, it adds little beyond the tool name itself, lacking nuance such as that the contact itself is not deleted.

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 provides no guidance on when to use this tool versus alternatives, such as 'add_contact_to_segment' or other contact management tools. There is no mention of prerequisites, context, or when not to use it.

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