zpa_list_app_connectors

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

Annotations already declare readOnlyHint: true. The description redundantly states 'read-only' but adds the capability of JMESPath filtering. It does not disclose pagination behavior, rate limits, or other runtime traits. The description adds some value beyond annotations but not extensively.

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 a single, concise sentence that front-loads the core purpose and key features. Every word is necessary; no redundancy.

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 6 parameters and many sibling tools, the description is adequate but lacks guidance on pagination, when to use this vs. 'zpa_get_app_connector', and how the output is structured. However, output schema exists, so return format details are not required.

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 100%, so baseline is 3. The description mentions JMESPath filtering for the 'query' parameter, which is already documented in the schema. It adds no substantial new meaning beyond the schema's parameter descriptions.

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 verb 'List', the resource 'ZPA app connectors', and the specific information included (status, version, health). It also notes the tool is read-only. The term 'app connectors' distinguishes it from sibling tools like 'zpa_get_app_connector' (single) and 'zpa_list_app_connector_groups' (groups).

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 mentions JMESPath filtering for client-side use, which indicates a use case, but it does not explicitly state when to prefer this tool over alternatives like 'zpa_get_app_connector' for single connectors or other list tools. No when-not or conditional guidance is provided.

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