zcell_get_sim_details

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

Explicitly states 'Read-only', aligning with the readOnlyHint annotation, and lists returned fields (ICCID, IMSI/IMEI, status, etc.), providing transparency about data content beyond the annotation.

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 concise sentences with no redundant phrasing; the first states the core purpose and the second adds read-only status and return field list, making it well-structured and efficient.

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 compensates by listing the return fields. It is complete for a simple getter, though it omits potential error conditions or usage caveats.

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 only parameter icc_id is described as the identifier used to fetch the record ('by ICCID'), clarifying its purpose beyond the schema's minimal 'Icc Id' label.

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?

Description clearly states the action ('Get') and resource ('full Zscaler Cellular record for one SIM'), and specifies the key identifier (ICCID), distinguishing it from list and location-group sibling tools.

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?

Implies usage when you need full details for a single SIM identified by ICCID, contrasting with list tools. Lacks explicit 'when to use' vs alternatives, but the context is clear enough.

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