reach_listSegmentContactsV1

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

The description discloses that it fetches and filters contacts by segment UUID, implying a read operation. With no annotations, the description carries the full burden but does not detail behaviors like pagination, error handling, or what happens if the segment doesn't exist. It adds some value beyond the schema but could be richer.

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 two sentences long, with the first sentence delivering the core purpose immediately. No extraneous information. It is highly concise and front-loaded.

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?

The description covers the main purpose and key parameter. For a simple list tool with no output schema and no annotations, it is mostly complete. However, it could mention the format of the returned contacts or any limits, but the basic functionality is clear.

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 100% with each parameter described. The description reinforces the role of segmentUuid but does not add new meaning for page and per_page beyond what the schema already provides. This meets the baseline for high coverage 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 it retrieves contacts associated with a specific segment. The verb 'Retrieve' is appropriate, and it distinguishes from siblings like reach_listContactsV1 by specifying the segment constraint. However, it does not explicitly differentiate from other contact-list siblings like reach_listProfileSegmentContactsV1.

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. The description does not mention when not to use it, prerequisites, or alternative tools for different filtering needs.

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