zms_get_resource_group_members

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

Matches annotations (readOnlyHint=true) with 'Read-only.' Also adds behavioral detail: 'Returns one row per member workload.' No contradictions.

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?

Four concise sentences with no wasted words. Purpose is front-loaded. Structure is efficient.

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?

Provides prerequisite and identifies the tool as list members, but does not describe the return fields or explain pagination parameters. With no output schema, more context on the response structure would be beneficial.

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 low (25%), yet description only adds context for group_id. Other parameters (query, page_num, page_size) are not explained beyond the schema. The schema does detail the query parameter, but the description does not compensate for the overall low coverage.

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 'List the members of a ZMS resource group' with a specific verb and resource. It distinguishes from sibling tools like 'zms_list_resource_groups' by mentioning how to obtain the group_id.

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?

Provides clear guidance: read-only, returns one row per workload, requires group_id from zms_list_resource_groups, and mentions required environment variable. Does not explicitly state when not to use or list alternatives, but context is adequate.

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