zia_list_devices

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

Annotations already declare readOnlyHint=true, and the description adds value by specifying pagination support and JMESPath client-side filtering, which are behavioral traits beyond what annotations provide. No contradictions with annotations.

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 sentence that front-loads the main action and key features. Every part is relevant and free of unnecessary words, achieving high conciseness and good structure.

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 the tool has 7 parameters all documented in the schema and an output schema exists, the description is adequate. It covers primary functionalities (filtering, pagination, JMESPath) but could mention the service parameter or output details. Still, it is sufficiently complete for this complexity.

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 100%, so baseline is 3. The description summarizes key parameters (name, user, pagination) but does not add significant new meaning beyond the detailed schema descriptions. It provides a high-level overview but no extra semantics.

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 ZIA devices with specific filtering options (name, user, pagination) and JMESPath support. It uses a specific verb 'List' and resource 'ZIA devices', distinguishing it from sibling tools like zia_list_devices_lite by mentioning read-only and JMESPath features.

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 for listing devices with filters, but does not explicitly state when to use this tool versus alternatives like zia_list_devices_lite or other list tools. No when-not or alternative guidance is provided.

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