get_zpa_posture_profile

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

Description adds only 'read-only', which is already provided by annotations (readOnlyHint=true). No additional behavioral context such as pagination, filtering behavior, or response format. Minimal value beyond annotations.

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?

One sentence is concise but under-informative. Front-loaded with core info, but the brevity sacrifices clarity and completeness. Could include more context without losing conciseness.

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 5 parameters, required action, nested objects in query_params, and existence of an output schema, the description is insufficient. It does not explain the action parameter's role, lookup methods, or output expectations, leaving gaps for agent usage.

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 coverage is 100%, so baseline is 3. Description adds no parameter-level explanation beyond what the schema already provides (e.g., action must be 'read', optional filters). No additional semantic value.

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?

Description states 'Manage ZPA Posture Profiles (read-only)', which clearly identifies the resource and that it's read-only. However, 'manage' is slightly vague; 'retrieve' would be more precise. Distinguishes from many sibling 'get_zpa_*' tools by specifying 'Posture 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 on when to use this tool versus alternatives. No mention of prerequisites, context, or exclusions. Among numerous sibling tools, explicit differentiation is missing.

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