list_segments

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

Despite no annotations, the description covers authentication (API key), concurrency limits (max 10), and idempotency (read-only, safe to retry), along with return format.

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?

Concise yet comprehensive; each sentence adds value. Structured with purpose first, then guidelines, behavior, parameter details, and return format.

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?

Complete coverage given 3 parameters and no annotations: includes purpose, usage, behavior, parameter specifications, and return format. No gaps.

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?

Adds significant meaning beyond schema: list_id format and source, count range with default, offset usage explanation. Compensates for 0% schema description coverage.

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 clearly states it lists segments and tags for an audience with member counts and types, and explicitly distinguishes from get_segment by noting that get_segment provides filter details.

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 case: 'discover segment IDs for campaign targeting or membership management.' Also directs to get_segment for full details, offering a clear alternative.

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