list_segments

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

Beyond annotations (readOnlyHint=true, destructiveHint=false), the description discloses important behavioral details: it returns both static and dynamic segments, includes member counts and types, and explains pagination with offset. No contradictions with annotations.

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?

The description is concise yet complete, with a clear structure: a purpose statement, a usage note, explicit args with descriptions, and a return format. Every sentence adds value without redundancy.

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?

Given the presence of an output schema and the detailed explanation of returns in the description, the tool is fully described. The description covers purpose, parameters, behavior, and return structure, making it complete for an AI agent.

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?

With 0% schema description coverage, the description adds substantial meaning for three of four parameters: list_id (format and source), count (range and default), offset (pagination usage). The account parameter is not described, but it is optional and default null. Overall, the description compensates well for the lack of schema descriptions.

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 the sibling get_segment by noting to use that for full details including filter conditions. It also mentions discovering segment IDs for campaign targeting, making the purpose precise and unique.

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 provides explicit guidance on when to use this tool (to discover segment IDs for campaign targeting or membership management) and when to use an alternative (get_segment for full details with filter conditions). It also mentions obtaining the list_id from list_audiences, which provides a clear prerequisite.

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