get_zpa_isolation_profile

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

The description repeats the read-only hint already provided by annotations, adding no new behavioral context. It does not disclose pagination, rate limits, or the fact that filtering is by exact name only. With annotations present, the description contributes minimal additional transparency.

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 sentence with no redundancy. It front-loads the action and resource, then adds the optional filter. Every word serves a purpose, and the structure is efficient.

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 tool has no output schema, but the description does not explain return values, pagination, or other common behaviors. However, for a simple list operation, the description provides the essential purpose. The lack of completeness is acceptable but not exemplary.

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 adds meaning to the undocumented 'name' parameter by stating it filters by exact name. The 'query' parameter has its own schema description, so the description complements the schema. With 50% schema coverage, the description partially compensates for the missing parameter documentation.

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 lists ZPA Cloud Browser Isolation (CBI) profiles, with optional exact name filtering. It specifies the resource (CBI profiles) and action (list), and the read-only nature is noted. This distinguishes it from sibling tools like zpa_list_isolation_policy_rules or zpa_get_isolation_policy_rule, which deal with rules not profiles.

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?

No guidance is given on when to use this tool versus alternatives. The description does not mention exclusions, prerequisites, or scenarios where another tool would be more appropriate. Given the large set of sibling tools, this is a significant omission.

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