preview_segment

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

Clearly states it does not save or send anything, and returns count and sample. No annotations provided, but description covers non-destructive nature and output. Could elaborate on auth needs or rate limits, but sufficient.

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 sentences, no unnecessary words. Front-loaded with key behavior (resolve without save/send), then details. Highly efficient.

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?

In absence of output schema, description explains return values (count and sample ≤10). Covers both input modes (segmentId or definition) and use case. Complete for a preview 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 coverage is 100%, so baseline is 3. Description adds structure details for 'definition' (inline {match, conditions[]}) beyond schema's generic type:object, improving clarity.

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?

Clearly states the tool resolves an audience without saving or sending, distinguishes from sibling segment tools like create_segment, update_segment, delete_segment, list_segments, get_segment.

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?

Explicitly says 'Use this to sanity-check a filter before attaching it to a campaign', implying when to use. Does not explicitly mention when not to use or alternatives, but context is clear.

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