get_zpa_scim_attribute

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

Annotations already declare readOnlyHint=true, so the description's 'read-only' is redundant. The description adds the two operational modes (list vs fetch by ID) but no further behavioral traits. No contradiction with 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?

The description is a single, front-loaded sentence of 16 words with zero waste. It efficiently conveys the core functionality.

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?

Lacking an output schema, the description does not explain return values or structure. For a 4-parameter tool, it omits details about search and query, though the purpose is clear. Adequate but could be more complete.

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?

With only 25% schema description coverage, the description partially compensates by implying idp_name is for 'named IdP' and attribute_id for 'fetch by ID'. However, it doesn't explain the search or query parameters beyond the schema's minimal query description.

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 or fetches ZPA SCIM attributes by IdP name or attribute ID, with explicit read-only verb. It distinguishes from siblings by specifying 'ZPA SCIM attributes', but does not explicitly differentiate from similar tools like get_zpa_saml_attribute.

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 SCIM attributes for a named IdP or fetching by ID, but provides no when-not-to-use guidance or alternatives. Among many similar sibling tools, this is a gap.

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