zcell_get_sim_location_group

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

The description reiterates 'Read-only,' matching the readOnlyHint annotation. It adds context about the extra fields returned but does not disclose potential side effects or error conditions. With annotations already covering read-only behavior, the description adds moderate value.

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?

Two sentences with no wasted words. The first sentence gives the core action, the second adds valuable details about the output. Efficient and front-loaded.

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 no output schema, the description compensates by listing key return fields (geo-fence, anomaly policies, ICCID buckets). It lacks information on possible errors or the specific format of group_id, but overall provides enough context for a get operation.

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 coverage is 0%, meaning no parameter descriptions are provided. The description fails to explain the group_id parameter or give examples, even though the parameter name is self-explanatory. With low coverage, the description should compensate but does not.

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 'Get one Zscaler Cellular SIM location group,' specifying the verb (Get) and resource (SIM location group). It distinguishes from sibling tools like zcell_list_sim_location_groups by focusing on a single entity retrieval.

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?

It explicitly marks the operation as 'Read-only' and details what additional data it returns (geo-fence, anomaly policies, ICCID buckets), implying it is used when these details are needed beyond summary fields. However, it does not explicitly state when to avoid using it or mention alternatives.

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