zdx_list_alert_affected_devices

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

The description states 'Read-only', which is consistent with the annotation, but adds little beyond that. It does mention 'Returns one identifying row per affected device', giving a minimal output expectation, but does not disclose any other behavioral traits such as pagination or error handling.

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 concise, using only two sentences to convey purpose, filters, and output format. Every word contributes meaning without redundancy or filler.

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?

The description gives enough to understand what the tool does and its basic output, but does not elaborate on response schema, pagination, or detailed usage context. For a simple read-only list operation, it is adequate but not comprehensive.

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 covers several parameters (location, department, geo, location groups, since) by describing their filter purpose, but does not explicitly name them or cover all parameters (limit, offset, query are omitted). It provides contextual meaning but lacks precise mapping to parameter identifiers.

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 'devices affected by a ZDX alert', making the purpose unambiguous. It also distinguishes this tool from other listing tools by specifying the ZDX alert context.

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 mentions read-only nature and provides filter hints (location/department/geo, location groups, since window), but does not explicitly state when to use this tool over alternatives or provide usage scenarios. It lacks explicit 'when not to use' guidance.

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