get_zia_user_departments

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

Annotations already declare readOnlyHint=true, and the description adds '(read-only)' which is redundant. It does add the two operational modes (list/fetch), but lacks details on pagination, error behavior, or response format. With annotations covering safety, the description provides minimal extra behavioral context.

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, front-loaded with the key action and resource. Every word contributes, with no filler or repetition.

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 9 parameters, no output schema, and low schema description coverage, this minimal description is insufficient. It does not address return values, parameter relationships, the distinction between 'list' and 'read_lite', or error handling, leaving the agent under-informed 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?

Schema description coverage is only 11% (only 'query' is described), and the tool description does not compensate. It mentions 'filters' and 'by ID' but does not map to the 9 parameters or clarify ambiguous ones like 'action' (read_lite) or 'limit_search'. The description adds little meaning beyond the schema itself.

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 action ('Read') and resource ('ZIA user departments'), and specifies two modes: 'list with filters' or 'fetch one by ID'. This distinguishes it from sibling tools like get_zia_users and get_zia_user_groups by resource and operation.

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 clear usage contexts: use when you need to list departments with filters or retrieve a single department by ID. It does not explicitly name alternatives or provide when-not-to-use guidance, but the two-mode framing offers sufficient context for selection.

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