zdx_list_alerts

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

The description reiterates read-only, which matches annotations. However, it adds no additional behavioral context such as pagination behavior, rate limits, or how filters combine beyond what annotations already provide.

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 extremely concise, front-loaded with the core purpose, and every word adds value. No unnecessary text.

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 8 parameters and an output schema, the description is minimal. It omits context on how parameters interact (e.g., time range with since, pagination with offset/limit). Could be more complete to aid agent understanding.

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 coverage is 100%, with descriptions for all 8 parameters. The description only mentions JMESPath filtering, which is already documented in the schema. No extra semantic value provided beyond the schema.

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 lists ZDX alerts and specifies it is read-only. It also mentions JMESPath client-side filtering, distinguishing it from siblings like zdx_get_alert or zdx_list_historical_alerts.

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 by stating the tool lists alerts, but does not explicitly guide when to use it versus alternatives like zdx_get_alert for a single alert or zdx_list_historical_alerts for historical data. No when-not or exclusions provided.

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