zcell_list_sim_location_groups

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

Annotations already declare readOnlyHint=true, and the description reinforces 'Read-only.' It adds information about the output structure and next steps. However, it does not disclose pagination behavior (despite page/size parameters) or rate limits, leaving gaps beyond what annotations 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 three concise sentences. The first defines the action, the second confirms read-only and specifies output, and the third provides actionable guidance. No unnecessary words.

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 no required parameters and no output schema, the description adequately covers the return structure and related tool. However, it omits explanation of pagination (page/size) and the name filter, which are relevant for list operations.

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 only 25% (only query has a description). The description does not explain the name, page, or size parameters, nor does it add meaning beyond the schema. For a tool with low coverage, the description should compensate but fails to do so.

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 Zscaler Cellular SIM location groups, specifies it is read-only, and details the output structure (one row per group with id, name, tracked ICCIDs). Distinguishes from sibling tools by its specific domain and purpose.

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 indicates the tool is for listing groups and advises using the returned id with zcell_get_sim_location_group for further details. While it does not explicitly contrast with other tools, the context of sibling tools (mostly from different Zscaler products) makes the usage clear.

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