get_zpa_scim_group

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

The description repeats the read-only annotation but adds no new behavioral details such as pagination behavior, error handling, or permission requirements. It is consistent with annotations but does not go beyond them in disclosing side effects or edge cases.

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, concise sentence that efficiently conveys the core functionality without redundancy. It is well-structured and easy to parse.

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 description adequately covers the essential operations and read-only nature. It does not mention output format or pagination, but for a simple read operation, it provides sufficient context for an agent to decide when to call it. The lack of explicit alternative guidance slightly reduces completeness.

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 maps scim_group_id to 'by ID' and idp_name to 'under a named IdP', adding meaning to those parameters. However, it does not explain page, page_size, or search (beyond the schema's existing JMESPath description). Schema coverage is low, and the description only partially compensates.

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 two primary functions: fetching a single ZPA SCIM group by ID or listing all groups under a named IdP. It explicitly includes 'read-only' and distinguishes this resource from other ZPA objects, making it unambiguous.

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 explains the two modes of operation (by ID or by IdP name) but does not explicitly contrast this tool with sibling tools like get_zpa_scim_attribute or zpa_list_pra_credentials. It lacks explicit 'when to use this vs. alternatives' guidance, though the resource specificity provides some implicit context.

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