delete_segment

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

Discloses irreversibility, concurrency limits (max 10), authentication via API key, respect for read-only/dry-run modes, and 404 error if segment missing. No annotations provided, so description carries full burden.

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?

Well-structured with paragraphs and sections. Information is efficiently presented, though slightly verbose with full examples. Clear and front-loaded.

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 no annotations and no output schema, the description covers all necessary context: what it does, when to use, parameters, return format, error handling, and constraints. Complete for a delete operation.

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?

Adds significant meaning beyond the schema: explains each parameter's purpose, gives format examples (10-char alphanumeric, numeric string), and tells how to obtain them via other tools. Schema has 0% description coverage, so description compensates fully.

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?

Clearly states it deletes a segment or tag from an audience, specifying that members remain. Distinguishes from siblings like update_segment and list_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?

Provides explicit when-to-use guidance: irreversible, suggests update_segment for modifications, and list_segments for finding IDs. Clearly indicates alternatives.

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