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

Annotations already declare destructiveHint=true, and the description adds specificity beyond that: 'Irreversible' and the cascading deletion of 'all its tags and classifications'. This tells the agent exactly what will be destroyed, which is valuable beyond the annotation.

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 compact: a summary sentence states the action, scope, and irreversibility, followed by a minimal returns block. No fluff, and the critical warning is 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?

With one parameter, full schema coverage, a clear destructive annotation, and the description covering scope, irreversibility, and the return value, nothing essential is missing. The returns block even specifies the confirmation payload format.

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%: the group_id parameter is described as 'The segment group to delete (from list_segment_groups).' The description adds no parameter-level detail beyond the schema, so the baseline of 3 applies.

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 states a specific verb ('Delete') and resource ('a segment group'), and clarifies it also removes 'all its tags and classifications', distinguishing it from sibling tools like delete_segment_tag. The 'Irreversible' warning adds meaningful scope. This is unambiguous and differentiated.

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 gives clear context that this tool is for deleting the whole group and its contents, not just a tag or classification. It does not explicitly name alternatives such as delete_segment_tag for partial deletion, but the scope is evident from the cascade description.

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