audience_list_segments

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety and purity profile is fully covered by structured data. The description's only added behavioral fact is that results are scoped to the server-side Audience credential, which is useful but thin given a zero-parameter, no-side-effect call.

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?

A single sentence with no filler, and the resource and scope are front-loaded. It stays within budget for a no-argument list call, though the brevity borders on being too sparse to guide an agent.

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 an output schema present, return values need no explanation, and with zero parameters the schema burden is nil; annotations cover safety. The only real gap is the absence of any cue about result volume, pagination, or relationship to audience_get_segment, which is minor for a simple low-complexity list 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?

The tool takes zero parameters, so the baseline of 4 applies; there is no parameter syntax for the description to document. Schema coverage is reported at 100% and the empty object schema is unambiguous.

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 (List) and resource (Audience segments), and adds a real scope qualifier: visibility is limited to what the server-side Audience credential can see. That distinguishes it from sibling readers like audience_get_segment and audience_list_pixels, though it does not name those siblings explicitly.

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 or when-not-to-use guidance and no mention of alternatives (e.g., use audience_get_segment for a single segment). The credential-scope phrase implies the tool returns everything visible rather than a filtered subset, but that is inference, not stated guidance.

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