audience.segments.list

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether this is a safe read, not pagination behavior, not rate limits, not result shape. For a tool with no annotation coverage this is a complete gap.

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?

It is short, but the brevity is under-specification rather than conciseness: the single sentence carries no usable content. Front-loading a scope and at least one filtering note would cost little and would actually earn its place.

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?

With five undocumented parameters, no annotations, and no output schema, the description leaves an agent without enough information to invoke the tool correctly or interpret its results. This is inadequate for the tool's actual complexity.

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% across five parameters (limit, types, fields, offset, statuses), and the description adds no semantics for any of them. The agent gets no hint about valid values, filtering behavior, or the meaning of limit/offset beyond their names.

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 restates the tool name with the namespace spelled out: 'Audience: list segments.' It confirms a list operation over segments, but adds nothing the name does not already convey and makes no attempt to distinguish this from siblings like audience.segments.get, audience.segments.stats, or audience.segments.overlap.

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?

There is no when-to-use guidance at all. With closely related siblings such as audience.segments.get and audience.segments.overlap available, the description gives no condition, scope, or prerequisite that would tell an agent when listing is the right operation.

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