get_zpa_saml_attribute

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

Annotations already provide readOnlyHint=true, and the description redundantly states 'read-only'. The description adds no further behavioral traits; it only mentions the scoping feature. This is adequate but not enriched beyond the 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?

Single sentence, front-loaded information, no wasted words. Every part earns its place.

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 covers the main purpose and key parameter, but without an output schema, it does not describe the return format or clarify what SAML attributes are. The 'query' and 'search' parameters are also not explained, though 'query' is documented in the schema.

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 33% (only 'query' documented in schema). The description only adds meaning for the 'idp_name' parameter, ignoring 'search' and not explaining 'query' beyond what schema provides. This leaves two out of three parameters without additional context.

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 it lists ZPA SAML attributes, with optional scoping to a named IdP. The verb 'list' and resource 'ZPA SAML attributes' are specific, and it distinguishes from sibling tools (no other tool specifically targets SAML attributes).

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 context via 'optionally scoped to a named IdP' but does not explicitly state when to use this tool versus alternatives or when not to use it. No exclusions are provided.

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