zia_list_time_intervals

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

Annotations include readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe read operation. The description adds no behavioral details beyond 'List', but it does not contradict the annotations, so the baseline transparency is adequate.

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, short sentence that is concise and front-loaded. However, it is under-specified for the tool's complexity, containing no details about parameters, output, or behavior beyond the action itself.

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 4 parameters, no output schema, and minimal annotations, the description is drastically incomplete. It does not explain what time intervals are, how pagination works, what the return format is, or when to choose this over the get_time_interval tool, making it insufficient for an AI agent to invoke correctly.

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 tool description adds no parameter information. Schema coverage is only 25%: the 'query' parameter has a detailed JMESPath description, but 'page', 'search', and 'page_size' lack explanations. The description does not compensate for this gap.

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 'List ZIA time intervals' states a clear action and resource, and the verb 'List' distinguishes it from the sibling 'zia_get_time_interval'. However, it essentially restates the tool name without adding extra context about what a time interval is or how it is used, making it minimally informative.

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. The description does not mention pagination, filtering, or differences from the related 'zia_get_time_interval' tool, leaving the agent to infer usage from context.

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