audience.segments.overlap

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. '(best effort)' usefully signals approximate/possibly incomplete results, but nothing is said about permission requirements, compute cost, rate limits, whether segment_ids must already exist, or what the response looks like.

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?

Very short and not padded, so nothing is wasted, but it is a single fragment rather than a front-loaded sentence with the essential scoping information. Being terse here reflects under-specification rather than disciplined conciseness.

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?

For a 3-parameter analytical tool with no annotations and no output schema, the description is far too thin. It omits the return shape (matrix vs top_pairs output differs by mode), any interpretation guidance for the overlap values, and how large segment_ids lists are handled.

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 67% with the mode enum values and limit default already documented in the schema, and segment_ids is self-explanatory as an array of IDs. The description adds no meaning beyond the schema, so the baseline 3 applies; it neither compensates nor subtracts.

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?

Names the resource (segments) and the operation family (overlap), so an agent can tell it computes pairwise intersection between audience segments. However it is phrased as a fragment ('Audience: overlap between segments') rather than a clear verb+object, and it does nothing to distinguish itself from the sibling audience.hf.overlap_matrix or audience.segments.stats.

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?

No statement of when to use this versus audience.hf.overlap_matrix, audience.segments.stats, or audience.segments.list. The parenthetical '(best effort)' hints the result may be approximate but gives no condition that would steer an agent toward or away from this tool.

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