zcell_list_sim_location_groups

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

Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds the output content (id, name, tracked ICCIDs) and the relationship to a sibling tool, which is useful context beyond the annotations. However, it does not disclose pagination behavior or any other side effects, and the read-only statement is redundant with the annotation. It adds some value but not extensive behavioral detail.

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 two sentences, front-loaded with the purpose, and every sentence adds value. No redundant or vague wording. It is a model of concise, effective tool documentation.

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 is a simple list operation, the description provides essential context: what it lists, the output fields, and how to get deeper details. It does not describe pagination, but that is captured in the schema. With no output schema, it partially describes the return format, which is sufficient for a list tool. It could mention the `query` parameter or filtering options, but the schema covers that.

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 does not explain any of the four parameters (name, page, size, query) other than indirectly referencing 'tracked ICCIDs'. Schema description coverage is only 25% (only query has a description), so the description must compensate, but it does not. There is no guidance on parameter semantics, making it hard for an agent to use filters or pagination correctly.

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 resource ('Zscaler Cellular SIM location groups'), and specifies the output structure ('Returns one row per group (id, name, tracked ICCIDs)'). It also distinguishes from sibling tools by directing to `zcell_get_sim_location_group` for detail, making the purpose unambiguous.

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 provides a clear context of use: listing groups, and explicitly tells when to use the sibling tool for detail ('Use the returned `id` with `zcell_get_sim_location_group` for the geo-fence and linked-policy detail'). It does not list exclusions or alternative usage scenarios, but the guidance is sufficient to differentiate this tool from its immediate sibling.

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