get_zpa_scim_attribute

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

The '(read-only)' confirmation aligns with readOnlyHint annotation, but 'Manage' could imply write operations. No additional behavioral details beyond annotation.

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?

Extremely short (5 words), but lacks valuable content. Conciseness is fine, but at the cost of completeness.

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 the complexity (5 parameters, output schema, ZPA service), the description is minimal and fails to explain how to use the tool effectively, e.g., required parameters, filtering, or return format.

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 description coverage is 100%, so parameters are already documented. Description adds no information about parameter usage beyond the schema.

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 SCIM Attributes (read-only)', clearly indicating the tool reads SCIM attributes. However, 'Manage' is generic and does not differentiate from sibling tools like get_zpa_saml_attribute or get_zpa_scim_group.

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, exclusions, or context for use.

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