get_zpa_app_protection_profile

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

Annotations already set readOnlyHint=true. The description adds the 'read-only' label, but does not provide additional behavioral context such as whether the name filter is exact match, case-sensitive, or if there are rate limits or pagination. Without annotations, this would be insufficient, but with annotations, the bar is lower and the description adds minimal extra value.

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 that is front-loaded and efficient. Every word serves a purpose, and there is no extraneous information. It is appropriately concise for a straightforward list tool.

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?

For a simple read-only list tool with no output schema, the description covers the core functionality but lacks details like default behavior without a name filter, whether it returns all profiles, or any error conditions. It is minimally adequate but could be more complete for an agent unfamiliar with the API.

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 'name' parameter by stating it can be used for filtering, which the input schema does not describe (50% coverage). The 'query' parameter is already fully described in the schema. Overall, the description partially compensates for the lack of schema documentation on the name parameter.

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 App Protection profiles with optional name filtering, and explicitly notes it is read-only. This provides a specific verb ('List'), resource ('ZPA App Protection profiles'), and a filtering scope ('by name'). It distinguishes from sibling tools that likely deal with other ZPA resources.

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 usage for listing profiles or filtering by name, but does not explicitly state when to use this tool versus alternatives (e.g., when to use other get_zpa_* tools). No when-not-to-use or alternative guidance is provided.

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