zms_list_resources

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

The description reinforces the read-only nature already indicated by annotations, and adds detail about the return format (one row per workload with specific fields) and prerequisite (ZSCALER_CUSTOMER_ID). No contradictions.

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 concise (3 sentences) and front-loaded with the main purpose, followed by key details in a logical order.

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?

Without an output schema, the description adequately explains the return format (fields and one row per workload) and mentions required configuration. It could improve by noting pagination defaults, but overall is fairly 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?

Schema coverage is low (9%), but the description adds meaning for 6 out of 11 parameters by listing filterable fields (name, status, type, provider, region, OS). However, it does not explain query, pagination, sort_order, or include_deleted 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 it lists ZMS resources (workloads) and specifies the fields returned, distinguishing it from sibling tools that list other entities like agents or app catalogs.

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 read-only operation and lists filterable fields, but does not explicitly contrast with alternatives or specify when to use this tool over others.

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