Delete a community segment

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds the meaningful operational constraint that confirm=true must be set, plus the note that it changes community state. It still doesn't say the deletion is irreversible or what happens to members assigned to the segment.

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?

Two short sentences with the destructive action and the confirm gate front-loaded; nothing is padded or buried. 'Changes community state' is slightly vague filler, but the size is appropriate for the operation.

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 non-idempotent destructive tool with no output schema, the description covers the core action and the confirm precondition but omits consequences: permanence, effect on segment members, and whether any cleanup or reassignment is needed. That is a meaningful gap for an irreversible 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?

Schema description coverage is 100%, so the schema already documents account, confirm, and segment_id fully. The description only restates the confirm requirement, adding no syntax, format, or ID-sourcing detail beyond what the schema provides — baseline 3.

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 and resource ('Delete a community segment'), which is clear and unambiguous. It does not, however, distinguish this tool from its close siblings such as create_community_segment, update_community_segment, or duplicate_community_segment, so the agent gets no routing help beyond the name.

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?

It gives one concrete usage condition — confirm=true is required for the user-requested action — which implies the confirmation workflow. But it never says when to pick this over update_community_segment or duplicate_community_segment, and gives no exclusions or alternative guidance.

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