zcell_list_audit_metadata

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

Annotations already mark readOnlyHint; description adds that it returns operation types and object types and their purpose in the search tool. 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?

Three short sentences; 'Read-only.' is redundant with the annotation but not excessive. The rest is directly informative.

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 usefully states what is returned (operation types and object types) and how they relate to the search tool. The query parameter is fully documented in the schema. Adequate for a simple read-only metadata listing.

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 description covers 100% of the single `query` parameter with detailed JMESPath guidance; tool description adds no param-specific info, so baseline 3 applies.

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 names a specific resource ('Zscaler Cellular audit filter vocabulary') and clearly states it returns valid operation types and object types for `zcell_list_audit_customers_search`, distinguishing it from sibling list 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?

The description implies when to use it: to discover the valid operation types and object types to pass to `zcell_list_audit_customers_search`. It doesn't explicitly exclude other uses or name alternatives, but its purpose is clear enough within the context of the sibling tools.

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