zcell_get_customer_data_handling

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

The annotations already provide readOnlyHint=true, so the 'Read-only' statement is redundant but reinforces the behavior. The description adds detail about the scope (ZCELL_CUSTOMER_ID) and the specific data returned, which goes beyond annotation basics. It does not mention any other side effects or requirements, but for a read-only get tool, this is adequate given the annotations cover safety.

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: the first states the purpose, and the second elaborates on the return data and scoping. It is front-loaded with the main action and resource, followed by concise details. Every sentence adds value without fluff or redundancy, making it highly 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?

Given the tool has no parameters, no output schema, and simple read-only behavior, the description provides a solid list of what is returned (identity, activation state, platform, regions, SIM counts, usage, linked cloud metadata). It does not mention error conditions, permissions, or pagination, but for a get-customer operation these are less critical. The description is complete enough for an agent to understand the tool's purpose and output.

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?

There are zero parameters in the schema, so the description carries the full burden of explaining what the tool uses as context. It explicitly mentions 'Scoped by ZCELL_CUSTOMER_ID', which tells the agent that the operation is implicitly scoped to the logged-in customer, adding meaning beyond the empty input schema. With no parameters, the description appropriately provides the necessary context without needing to explain individual parameters.

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 action (Get) and the resource (logged-in Zscaler Cellular customer's profile and SIM totals). It enumerates specific data fields returned (identity, activation state, platform, regions, SIM counts, current usage, linked ZIA/ZPA metadata), which distinguishes it from sibling tools like zcell_list_sims or zcell_get_sim_details that focus on individual SIMs or lists.

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 this tool returns the logged-in customer's profile and SIM totals, and mentions it is scoped by ZCELL_CUSTOMER_ID, implying it is used when you need overall customer context. It does not explicitly name alternatives or exclusion criteria, but the clear scoping and focus on customer-level data provide sufficient context for when to use it versus more granular SIM-focused tools.

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