Remove Segment

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

No annotations are provided, so the description carries the full burden. It mentions that removing a segment is irreversible, but does not disclose other behavioral traits such as potential side effects (e.g., impact on contacts in the segment), required permissions, or error conditions. The irreversibility is noted, but more context would be beneficial.

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 compact (three sentences) and front-loaded with the purpose, followed by critical usage guidelines. Every sentence adds value, and there is no 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?

Given the simplicity of the tool (one parameter, no output schema, no annotations), the description adequately covers purpose and usage. It lacks details about the response or prerequisites (e.g., segment must exist), but these are implied. Slightly more completeness could be achieved by mentioning the expected outcome, but it is sufficient.

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 coverage is 100%, so baseline is 3. The description does not add any additional meaning beyond the schema; it simply says 'by ID' which is already implicit from the parameter description. No extra semantic value is provided.

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 clearly states 'Remove a segment by ID from Resend.' It specifies the action (remove), the resource (segment), and the identifier (by ID). This distinguishes it from sibling tools like 'remove-contact-from-segment' or 'create-segment'.

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 explicit instructions: 'Before using this tool, you MUST double-check with the user...' including referencing the segment name, warning about irreversibility, and requiring explicit confirmation. This is excellent guidance on when and how to use the tool.

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