zpa_list_ba_certificates

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

The annotation already declares readOnlyHint=true, and the description merely repeats 'read-only' without adding any additional behavioral context such as return format, pagination behavior, or side effects. It adds no value 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?

The description is a single concise sentence that directly states the purpose with no extraneous words or fluff. It is optimally brief.

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 simplicity of the operation, the description is minimal but lacks essential usage context: it does not mention how to handle pagination, filter results, or when to use this instead of the get endpoint. It is not complete enough for an agent to use effectively without additional schema exploration.

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?

The description does not explain any of the parameters (page, query, search, page_size, microtenant_id). While the schema provides a detailed description for 'query', the other parameters lack context, and the description does not compensate for the low schema coverage.

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 verb 'List' and the resource 'ZPA Browser Access certificates', which is specific and distinguishes it from related get/list operations like zpa_get_ba_certificate. It is immediately understandable.

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 that this tool is used to list all BA certificates, but it does not explicitly mention when to use this versus other similar list tools or the get variant. It lacks guidance on alternatives, pagination, or filtering.

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