zpa_list_ba_certificates

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

Annotations already declare readOnlyHint=true, and the description merely repeats 'read-only'. No additional behavioral traits (e.g., pagination, rate limits, response format) are disclosed beyond what annotations provide. The description adds minimal value.

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 very short (one sentence) and front-loaded, but it is minimally informative. While not verbose, it sacrifices completeness for brevity.

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 tool is simple but has under-documented parameters and no output schema. The description does not clarify return values, filtering capabilities, or the effect of parameters like 'search' and 'microtenant_id'. This leaves significant gaps for correct invocation.

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 input schema has three parameters, but only 'query' has a detailed description within the schema (33% coverage). The description itself does not mention or explain any parameters, failing to compensate for the undocumented 'search' and 'microtenant_id' parameters.

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 'List' and resource 'ZPA Browser Access certificates'. The annotation readOnlyHint confirms read-only nature, but the description explicitly repeats it. It is distinct from the sibling 'zpa_get_ba_certificate' which retrieves a single certificate.

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 is provided on when to use this tool versus alternatives. The sibling tool 'zpa_get_ba_certificate' exists but is not mentioned. The description does not specify context or prerequisites.

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