Remove Segment

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

With no annotations provided, the description fully discloses the irreversible nature of the action and the necessity of a confirmation step. It warns that removal cannot be undone, which is critical behavioral information beyond what the schema conveys.

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, front-loaded with the core action, and every sentence serves a purpose: the action, the mandatory double-check, the irreversibility warning, and the explicit confirmation requirement. No unnecessary words.

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 delete operation with one parameter and no output schema, the description covers all necessary context: what it does, how it must be used safely, and the irreversible consequence. It is fully self-contained.

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 already describes the 'id' parameter as 'Segment ID', so baseline is 3. The description adds the instruction to reference the segment NAME during double-checking, implying the need to map id to a human-readable name. This enriches the id parameter's meaning beyond the schema, though not extensively.

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 starts with 'Remove a segment by ID from Resend,' which clearly states the action (remove), the target resource (segment), and the identifier (ID). It unambiguously distinguishes this tool from sibling remove tools like remove-contact or remove-broadcast by specifying the resource.

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 when-not-to-use guidance: it must only be used after the user explicitly confirms. It also mandates a specific pre-operation workflow (double-check, reference the segment name, warn about irreversibility), leaving no ambiguity about the required confirmation process.

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