zpa_get_ba_certificate

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

The description redundantly states 'read-only', which is already declared in annotations via `readOnlyHint: true`. It adds no new behavioral context beyond what annotations already provide, but does not contradict them.

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, well-structured sentence that immediately conveys the tool's purpose and key constraint. Every word is meaningful and front-loaded.

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 tool's simplicity, the presence of an output schema, and annotations covering safety, the description is complete. It covers what, how, and the read-only nature, leaving no significant gaps.

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 coverage is 100%, so parameters are well-documented in the schema. The description mentions 'by ID', which reinforces the `certificate_id` parameter but adds minimal value beyond the schema 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 action (Get), the resource (specific ZPA browser access certificate), and the identifier method (by ID). It distinguishes this tool from its sibling `zpa_list_ba_certificates`, which retrieves all certificates.

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 indicates when to use the tool (when you have a specific certificate ID) and notes it's read-only. However, it does not explicitly mention when not to use it or provide alternatives like the list tool.

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