get_zia_user_groups

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

The description adds 'read-only' which aligns with the readOnlyHint annotation but provides no additional behavioral context. It does not disclose pagination, result ordering, or any potential side effects beyond the read-only nature. Given the annotation already covers safety, the description adds minimal value here.

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 a single, front-loaded sentence that efficiently conveys the tool's core functionality without any fluff. Every word earns its place.

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 has 9 optional parameters and no output schema, the one-line description is insufficient. It fails to mention return format, pagination behavior, default sorting, or any constraints, leaving the agent without critical operational context for correct invocation.

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 maps three usage scenarios to parameters (group_id for 'fetch by ID', name for 'find by name', and no params for list) but does not explain the other six parameters (page, page_size, sort_by, sort_order, defined_by, search). With schema description coverage at only 11%, the description should compensate more for the missing parameter semantics, but it only partially does.

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 reads ZIA user groups and enumerates three modes: fetch by ID, find by name, or list. This is specific and distinguishes it from sibling tools like get_zia_users and get_zia_user_departments, which target different 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?

While the description indicates what the tool does, it offers no guidance on when to choose this tool over alternatives such as zid_get_user_groups or zid_get_user_groups_by_name. There is no mention of prerequisites, mutually exclusive modes, or when a particular mode is appropriate.

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