zia_list_shadow_it_apps

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

The description is consistent with the readOnlyHint and says 'List', but it adds almost no behavioral context beyond the annotation. It does not mention pagination behavior, response format, or any caveats about the returned records, aside from parameter-level advice in the query schema.

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 main description is a single, focused sentence with no filler. The query parameter description is long, but every sentence adds practical value, and the overall structure places the tool's core purpose first.

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 no output schema and only a terse main description, the tool definition omits important context such as return shape, pagination semantics, and relationship to overlapping siblings. The detailed query parameter helps but is not enough to make the tool definition complete for an agent unfamiliar with ZIA Shadow IT APIs.

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?

While schema coverage is only 33%, the 'query' parameter description is exceptionally detailed: it explains JMESPath usage, gives examples, warns about snake_case vs camelCase field names, and advises an initial unfiltered call. Limit and page_number have no descriptions, but their names and defaults make them reasonably self-evident.

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 verb ('List') and the resource ('ZIA Shadow IT applications') with a parenthetical qualifier ('analytics catalog') that adds context. It is specific enough to identify the tool's function, though it does not explicitly differentiate it from the similarly named sibling zins_get_shadow_it_apps.

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 guidance on when to use this tool versus alternatives such as zins_get_shadow_it_apps or zia_list_shadow_it_custom_tags. The only usage advice concerns the 'query' parameter (JMESPath usage), which is parameter-specific rather than tool-selection guidance.

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