Duplicate a community segment

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the mutation and irreversibility profile is covered structurally. The description adds the confirmation gate ('Changes community state and requires confirm=true'), which is useful but overlaps the confirm parameter description, and it says nothing about what the duplicate copies or whether the source segment is affected.

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, front-loaded with the operation and followed by the confirmation constraint. No wasted words, though the second sentence is somewhat terse.

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?

No output schema, so the description does not need to explain return values, and annotations plus the schema cover safety and parameters. However, for a destructive duplicate operation the definition omits what the new segment inherits and whether the source is untouched, leaving a moderate gap.

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 both required and optional parameters are documented in the schema itself. The description adds no parameter-level detail (e.g., what is copied vs. overridden by the new title), 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?

States a specific verb ('duplicate') and resource ('community segment'), so an agent can distinguish it from create_community_segment, update_community_segment, and delete_community_segment. It stops short of explicitly differentiating itself from those siblings, but the operation is unambiguous.

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 notes that confirm=true is required 'for the user-requested action,' which implies a usage precondition. It offers no guidance on when to duplicate vs. create a new segment, or any other alternative, so the guidance is only partial.

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