reach_listSegmentContactsV1

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

No annotations provided, so the description bears full responsibility. It describes the operation as 'fetch and filter', indicating a read-only action, but fails to disclose behavioral traits such as pagination behavior, rate limits, or any side effects. It does not contradict any annotations as none exist.

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 short and direct, with no fluff. It is front-loaded with the main action. Could potentially be more structured but is acceptable for this simple tool.

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?

While the tool is simple with 3 parameters and no output schema, the description does not explain pagination behavior or the return format. For a retrieval tool that returns a list, this information is important for effective use. The description feels incomplete.

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 100%, so baseline is 3. The description adds minimal value by confirming segmentUuid is a UUID, which is already in the schema. No additional semantics for page and per_page parameters. Baseline score is appropriate.

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 the verb 'Retrieve' and the resource 'contacts associated with a specific segment'. It distinguishes from sibling tools like reach_listContactsV1 (all contacts) and reach_listSegmentsV1 (all segments) by explicitly linking to a segment UUID.

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?

The description implies usage when you have a segment UUID and need its contacts, but does not explicitly state when to use this tool vs alternatives (e.g., reach_listContactsV1 for all contacts) or when not to use it. No exclusions or prerequisites mentioned.

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