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

With no annotations, the description carries the behavioral burden. It usefully discloses that membership evaluation happens server-side and matches the admin CRM's behavior, which tells the agent this is not just a stored membership list but a computed rule match. It does not mention ordering, auth, or error behavior, but the key semantic is covered.

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?

A single sentence that conveys the core operation, the selection mechanism, and the behavioral guarantee without wasted words. The most important information is 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?

For a simple list operation with fully documented parameters, the description is nearly complete. It could additionally clarify what member fields are returned or whether pagination follows standard offset/limit semantics, but the schema already documents limit and offset defaults and bounds.

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%, and each parameter (segment_id, limit, offset) already has a meaningful description. The tool description adds no extra parameter-level guidance, so the baseline of 3 applies.

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?

Uses a specific verb ('List') and a precise resource ('members matching a segment's rules'), which clearly distinguishes it from sibling tools like hivelearn_list_segments (which lists segments) and hivelearn_list_members (which lists all members). The phrasing leaves no ambiguity about what is returned.

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 establishes clear context: use this tool when you need the members that satisfy a segment's rules rather than a general member list. It does not explicitly name alternatives or state when not to use it, but the 'segment's rules' phrasing strongly implies the selection criteria.

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