get_zpa_posture_profile

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

The read-only behavior is already declared via annotations (readOnlyHint=true), and the description redundantly repeats 'read-only', which adds no new information. It does disclose the capability to look up by ID or name, which is a behavioral detail beyond the annotations. However, it doesn't mention pagination, error handling, or return format. Given the annotations cover the safety profile, this is adequate but not rich.

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, clear sentence with no fluff. It front-loads the core action and resource. It is concise and easy to parse, but it could benefit from a brief note on pagination or alternative usage. Still, it achieves conciseness without sacrificing primary clarity.

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 tool with 5 parameters and no output schema, this description is underspecified. It lacks information about result pagination (page, page_size), the effect of the query parameter for filtering, and return structure. While the annotations confirm read-only status, the description does not guide the agent on how to use the tool effectively beyond the basic list/lookup. The detailed query parameter description in the schema partially mitigates this, but the overall description remains incomplete.

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 mentions 'by ID or name', hinting at the profile_id and name parameters, but does not explain page, page_size, or query parameters. Schema description coverage is only 20%, so the description should compensate, but it adds minimal parameter meaning. The query parameter has a detailed schema description, but that's from the schema, not the tool description. The description fails to clarify how pagination or filtering works, leaving ambiguity.

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's function: listing ZPA posture profiles or retrieving one by ID or name. It specifies the resource (posture profiles) and the actions (list or lookup), and distinguishes it from other similar tools by naming the specific ZPA entity. The read-only qualifier adds clarity about the operation's nature.

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. There is no mention of prerequisites, conditions for using list vs. lookup, or trade-offs against other profile-related tools. The short sentence leaves the agent to infer usage solely from the tool name and description, which is insufficient for complex decisions.

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