ztna_group_users

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

Annotations already declare readOnlyHint=true, so the "[READ]" prefix adds nothing. Beyond that, the description says nothing about pagination behavior despite limit and page_offset parameters, nor about what happens with an invalid group or whether assignments are user-level or device-level. The description carries no behavioral load at all.

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?

It is a single short sentence with no filler, which is structurally clean, but the brevity is under-specification rather than economy — nothing is front-loaded because almost nothing is said.

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?

With four undocumented parameters, no output schema, and only a readOnly annotation, the description should explain pagination, required identifiers, and the shape of the result. None of that is present, so an agent cannot call this confidently beyond guessing.

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 0% for all four parameters. The phrase "group users" weakly implies group_id, but provider_id, limit, and page_offset are entirely unexplained in both the schema and the description, including whether page_offset is a token or an index.

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 gives a verb ("List") and a resource ("assigned group users"), so the basic operation is inferable, but it never states what a "group" is here or how this differs from siblings like ztna_group, ztna_users, or ztna_role_bindings. It would be easy to confuse with a group-detail tool.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g. that a provider and group must exist), and no pointer to an alternative tool for listing all users. The agent must infer everything from the name.

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