List Segment Contacts

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

With no annotations, the description carries the burden. It states the behavior (listing) plainly and implies a read-only operation, but it does not disclose any additional traits such as pagination, sorting, or required permissions. The simplicity of the operation mitigates the lack of detail, but there is room for improvement.

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 one short sentence that immediately conveys the core purpose. There is no wasted text, and it is front-loaded with the action verb.

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 simple single-parameter list operation, the description adequately captures the tool's purpose. However, it omits any information about the response format or how it differs from similar reach tools, which is a minor gap. Given the low complexity, it is nearly complete.

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 schema already provides a 100% description for the single parameter (segment_uuid as 'Segment UUID'). The description adds no additional information about the parameter, so it meets the baseline but does not enhance understanding.

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 a specific operation: listing contacts within a given segment. It uses a clear verb and resource, and the title is consistent. It distinguishes this from reach_contacts_list (all contacts) and reach_segments_list (segments) by specifying 'in a segment'.

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 guidance is provided on when to use this tool versus alternatives like reach_contacts_list or reach_segments_get. The description only restates the function without any context or exclusions, leaving the agent to infer appropriateness.

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