get_zpa_isolation_profile

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

Annotations already provide readOnlyHint=true. The description adds no behavioral context beyond stating read-only. It does not disclose rate limits, authentication needs, or other traits. With annotations present, the description adds minimal value, scoring at baseline.

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 short sentence, which is concise but lacks detail. It fits the tool's simplicity but does not fully leverage the opportunity to add value. The sentence is not particularly front-loaded with critical info.

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's simplicity, good schema coverage, and presence of annotations and output schema, the description is minimally adequate. However, it does not explain the return format or provide context on when to use this tool among many siblings, so completeness is average.

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 coverage is 100%, with each parameter described clearly (action: only 'read', name: full name to search, service: default 'zpa'). The description adds no additional meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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 states the tool manages ZPA Cloud Browser Isolation profiles as read-only, which clarifies its purpose. However, 'Manage' is a broad verb; 'Retrieve' or 'List' would be more precise. The name and description together clearly indicate it's for reading CBI 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?

The description provides no guidance on when to use this tool versus alternatives, such as when to use get_zpa_isolation_policy_rule or other sibling tools. It does not mention that modifications require different tools or any context for selection.

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