zpa_get_pra_credential

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

Description adds 'read-only' which matches the annotation readOnlyHint=true, but does not disclose additional behavioral traits beyond what annotations provide. The annotation already conveys safety; description adds only the 'by ID' constraint, which is more about parameter usage. No contradictions.

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 that is concise and front-loads the purpose. No extraneous words or information. Efficiently communicates the core function.

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?

For a simple read-only retrieval by ID with a single required parameter and an output schema, the description is sufficient. It covers the essential: what it does and that it's safe. Lacks explanation of what a PRA credential is, but given sibling naming and typical use, it's complete enough.

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?

Input schema has 3 parameters with 100% description coverage. The tool description mentions 'by ID', which aligns with the required credential_id. However, it does not add extra meaning beyond the schema descriptions. Parameter semantics are adequate but not enhanced.

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 clearly states verb 'Get', resource 'ZPA PRA credential', method 'by ID', and adds 'read-only' to indicate safety. Differentiates from sibling tools like zpa_list_pra_credentials which list all, and other ZPA get tools by specifying the exact credential resource.

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 explicit when-to-use or when-not-to-use guidance. The description implicitly suggests use for getting a single credential by ID, but does not mention alternatives like zpa_list_pra_credentials for listing. For a simple retrieval, this may be acceptable, but lacking explicit guidance reduces score.

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