zpa_list_app_connectors

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

The annotation 'readOnlyHint: true' already signals a safe read operation. The description adds 'with health/status' which gives extra behavioral context beyond the annotation. However, it does not disclose other behaviors like pagination or rate limits. Given the annotation reduces the burden, a score of 3 is appropriate.

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 with no redundant information. It efficiently conveys the core purpose without extra words.

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?

The description covers the basic purpose but omits details such as return format, pagination behavior, and filtering options. Given its simplicity (no output schema), it is minimally adequate but could provide more context for an agent to use effectively.

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 input schema has 5 parameters, with only 20% having descriptions (the 'query' parameter). The description does not mention any parameters or their usage, leaving the agent to rely solely on the schema, which is insufficient for the undocumented 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 ('List'), the resource ('ZPA app connectors'), and the specific context ('with health/status (read-only)'). It effectively distinguishes from sibling tools like 'zpa_get_app_connector' (single item) 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 lacks any guidance on when to use this tool versus alternatives. No explicit when-to-use, when-not-to-use, or mention of alternative tools for filtering or other operations. The user must infer usage from the name alone.

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