zms_get_resource_group_members

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

The description reinforces the read-only annotation, clarifies the output row granularity ('one row per member workload'), and exposes the ZSCALER_CUSTOMER_ID requirement. It adds useful behavioral context beyond the annotations, though it doesn't discuss pagination behavior.

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 compact and front-loaded with the core purpose. Every sentence adds value: the read-only note, output shape, parameter source, and required credential. No filler or redundancy.

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?

Given the tool's simplicity, the description covers the purpose, output granularity, key parameter provenance, and auth requirement. It lacks pagination behavior details, but the defaulted page parameters and low complexity make this a minor gap.

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 description adds meaning for group_id by pointing to zms_list_resource_groups, and the schema already covers the query parameter in detail. However, page_num and page_size have no semantic explanation, and with only 25% schema coverage, the description could compensate more for the undocumented parameters.

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 tool lists members of a ZMS resource group and adds that it returns one row per member workload, distinguishing it from sibling tools like zms_list_resource_groups. The verb 'List' and specific resource scope make the purpose unambiguous.

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?

It gives clear context: obtain group_id from zms_list_resource_groups and requires ZSCALER_CUSTOMER_ID. It does not explicitly name alternatives or when-not-to-use, but the usage context is strong for a list-by-group operation.

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