Update segment

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

Annotations already declare idempotentHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds genuinely useful non-schema context: changing a DYNAMIC segment's condition alters its membership and therefore campaign reach. Minor gaps remain – no mention of permissions or how STATIC vs DYNAMIC segments behave on update.

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?

Bolded section headers front-load purpose, exclusions, return, and impact, and every sentence is load-bearing. Slightly heavy on markup for the amount of content, but not padded.

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 mutation tool with annotations and no output schema, the description covers purpose, exclusions, return shape, and a meaningful side-effect warning. It stops short of explaining the STATIC/DYNAMIC type field or trackMembership, which an agent editing a segment would benefit from.

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 0%, so the description must carry parameter meaning. It names name, description and 'filter condition', partially compensating, but leaves id (the only required param), type, and trackMembership undocumented, and gives no guidance on the nested condition object structure.

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 (change) and resource (segment), and enumerates the mutable fields (name, description, filter condition). The 'Not for' line names the sibling tools (plunk_add_segment_members, plunk_remove_segment_members) so the agent can distinguish member management from segment attribute editing without opening any schema.

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 'Use when' (refining dynamic segment matches) and 'Not for' clauses with named alternatives. The routing between attribute updates and membership operations is fully specified, leaving nothing to inference.

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