zia_list_locations

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

The description adds no behavioral detail beyond the readOnlyHint and openWorldHint annotations; it does not mention pagination, output fields, or response shape. The schema's query parameter description provides caveats about snake_case field names, but that is structured schema content, not the tool description.

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 one short sentence with no filler and a clear verb and object. It is appropriately terse, though it could have included a brief scope note or pointer to related tools without losing conciseness.

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, the description should provide some indication of what a location is or what fields are returned, but it only names the resource. The query parameter description offers useful filtering guidance but does not make the overall description complete.

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 main description does not mention either parameter. The 'query' parameter has a thorough schema description, but 'search' is entirely undocumented, and with 50% schema description coverage the description does not compensate for the missing parameter meaning.

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 action ('list') and the resource ('ZIA locations'), which is enough to distinguish it from sibling tools like zia_list_location_groups and zia_get_location. However, it is minimal and does not specify the scope of the listing (e.g., all locations, pagination behavior).

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?

No guidance is given on when to use this tool versus alternatives such as zia_get_location or zia_list_location_groups. There are no use cases, prerequisites, or exclusions, leaving the agent to infer intent from the tool name and sibling list.

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