zcell_list_sims

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

The description states read-only behavior and mentions pagination envelope, adding value beyond the readOnlyHint annotation. No contradictions or additional behavioral gaps noted.

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?

Three front-loaded sentences with no fluff. Purpose, behavior, and filters are efficiently conveyed.

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 and 15 parameters, the description gives a high-level view but lacks detail on return format, optionality combination, and constraints. For a complex tool, it is adequate but not complete.

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 lists filter categories (ICCID, status, etc.) covering many parameters, but schema coverage is low (7%) and several parameters (e.g., brand_name, ip_address, pagination) are only implicitly referenced. Some meaning is added but not comprehensive.

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 searches the Zscaler Cellular SIM inventory with filters and pagination, and distinguishes it from sibling tools like zcell_get_sim_details by specifying inventory browsing.

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 usage for browsing SIM inventory but does not explicitly differentiate from alternatives (e.g., zcell_get_sim_details) or provide when-not-to-use guidance.

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