List profile segment contacts

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds scoping and filtering context but does not disclose additional behavioral details such as pagination limits, response format, authentication needs, or rate limits.

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, but the second sentence largely restates the first: both mention fetching contacts, a specific segment, and profile scoping. The added 'identified by its UUID' detail is minor, so the description could be reduced to one efficient sentence.

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 required inputs and read-only nature are clear, and pagination parameters are present in the schema. However, with no output schema, the description does not explain the return shape or pagination behavior, and it does not differentiate this tool from closely named sibling list tools.

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%, with each parameter having a basic description. The tool description reinforces that segmentUuid identifies the segment and profileUuid scopes the request, but this is only marginally more informative than the schema already provides.

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 verb and resource: 'Retrieve contacts associated with a specific segment for a given profile.' It identifies the profile and segment scoping, which distinguishes it from more general list tools, though it does not explicitly name or contrast sibling tools.

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 gives context by explaining that contacts belong to a segment identified by UUID and are scoped to a profile, implying when this tool is appropriate. However, it does not explicitly say when to use this instead of closely related siblings like reach_listSegmentContactsV1 or reach_listProfileContactsV1.

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