zms_list_resource_groups

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

Annotations already declare readOnlyHint=true. The description adds that it returns one row per group with fields, and requires ZSCALER_CUSTOMER_ID. This adds some context beyond annotations, though no further behavioral details like rate limits are provided.

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 concise, two sentences, and front-loaded with the purpose. It efficiently conveys the output format, though it could list parameters for better structure.

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?

No output schema exists, so the description's mention of output fields is helpful. However, it lacks guidance on pagination, filtering, or the meaning of parameters, making it incomplete for practical use.

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 coverage is low (20%), yet the description does not describe any of the 5 parameters (name, query, page_num, page_size, resource_hostname). It fails to add meaning beyond the schema, missing a chance to explain input semantics.

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 it lists ZMS resource groups and specifies the output fields (id, name, type, etc.). It is a specific verb+resource, though it does not explicitly differentiate from sibling list tools like zms_list_agent_groups or zms_list_resources.

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 notes it is read-only and requires ZSCALER_CUSTOMER_ID, but provides no guidance on when to use this tool versus alternatives. No explicit when/not or alternative tools are mentioned.

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