Delete a saved segment or cohort

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

Beyond destructiveHint=true, the description discloses 'Permanently delete', 'This cannot be undone', and 'There is no undo', clearly communicating irreversibility and the need for confirmation. It also supplies the return shape. It does not discuss repeated-call behavior, but that is covered by idempotentHint=true, and the description does not contradict the annotations.

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 front-loaded with the core purpose, followed by a one-line warning and compact Args/Returns sections. It is slightly redundant with the input schema's parameter descriptions, but it remains short and well organized.

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?

With no output schema, the Returns block fills an important gap by stating the exact success shape. The description also covers the ID discovery prerequisite, the required confirm flag, and the irreversible destructive nature. Nothing essential is missing for a low-complexity 3-parameter delete tool.

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%, so the schema already documents all three parameters, including the report_id source and the confirm=true requirement. The description's Args section largely repeats that information without adding new semantics, so it stays at the baseline for fully-covered schemas.

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?

States a specific verb and resource: 'Permanently delete a saved Segment or Cohort', with a concrete outcome ('no longer appears in the Umami UI'). The target is unambiguous and clearly separated from sibling delete tools such as umami_delete_website, umami_delete_user, and umami_delete_saved_report.

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 first sentence establishes the intended use, and 'Get the ID from umami_list_segments_cohorts' gives an explicit prerequisite. 'Requires confirm=true' is a clear precondition. It does not explicitly mention when not to use this tool or contrast it with related deletion siblings, so it falls just short of a 5.

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