zia_get_workload_group

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

The annotations already declare readOnlyHint true, and the description aligns with a read-only retrieval. No additional behavioral details (e.g., error handling, return format) are provided, but the read-only nature is covered, so the description adds minimal extra context beyond the annotations.

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, concise sentence with no redundant wording or filler. It is front-loaded with the action and resource, making it exceptionally 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?

For a simple get-by-ID tool, the description is adequate but lacks details such as the parameter format, return value structure, or behavior for non-existent IDs. Given the absence of an output schema and 0% parameter schema coverage, the description could be more informative, but it still fulfills the basic purpose.

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 says 'by ID', which clarifies that group_id is the unique identifier, but it does not specify the format or provide examples. Since schema coverage is 0%, the description provides minimal compensation, though the parameter name is self-explanatory for a typical get-by-ID operation.

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 'Get a single ZIA workload group by ID', using a specific verb and resource, and explicitly distinguishes from listing all workloads groups (zia_list_workload_groups). It is concise and unambiguous, leaving no doubt about the tool's function.

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 implies usage for retrieving a single workload group by its ID, contrasting with the list operation. However, it does not explicitly mention when to avoid using it or name the alternative tool, though the sibling list tool is obvious and the wording makes the intent clear.

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