get_zpa_enrollment_certificate

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

The description only states 'read-only', which duplicates the annotation readOnlyHint=true. It adds no additional behavioral context such as authentication requirements, rate limits, or result structure, providing minimal added 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 a single concise phrase with no wasted words. It is appropriately front-loaded and avoids redundancy, though it could be slightly more informative.

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 has 5 parameters, an output schema, and many siblings, the description is too sparse. It lacks context about the role of enrollment certificates, expected results, or how parameters interact, making it incomplete.

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 100%, so the baseline is 3. The description does not add extra meaning beyond the schema's parameter descriptions, thus scoring exactly at baseline.

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 states 'Manage ZPA Enrollment Certificates (read-only)', combined with the tool name, clearly indicates the tool retrieves enrollment certificates. However, the verb 'Manage' is slightly broad for a read-only tool, preventing a top score.

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 usage guidelines are provided. The description does not explain when to use this tool versus the many similar sibling tools like 'zpa_get_ba_certificate', nor does it specify prerequisites or conditions.

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