zcell_get_customer_data_handling

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

Description declares 'Read-only', matching the readOnlyHint annotation, and lists the returned fields (identity, activation state, etc.), adding value beyond the annotation by specifying the data content and scope.

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, front-loaded with purpose and immediately followed by detailed return info and scope. No redundant 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?

Despite no output schema, the description enumerates all key return fields (identity, activation, platform, regions, SIM counts, usage, linked metadata) and mentions scope, making it complete for a profile retrieval tool with zero parameters.

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?

No parameters exist, so schema coverage is 100%. The description doesn't need to add parameter meaning; baseline 4 is appropriate.

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 retrieves the logged-in Zscaler Cellular customer's profile and SIM totals, using the specific verb 'Get' and naming the resource. It distinguishes this tool from siblings by specifying the ZCELL_CUSTOMER_ID scope and focusing on customer data, which is unique among the listed siblings that cover different products or data types.

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 implies this tool is for obtaining the overall customer profile (read-only), but does not explicitly state when to use alternatives like zcell_list_sims for SIM details. However, given the diverse sibling tools, the context is clear enough for correct selection.

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