vpn_certificate_ocsp_server_list

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

The description only states 'list', which implies a read operation, but no annotations are present to confirm. No behavioral details are given, such as whether it requires super-admin, returns all records or paginated, or if it affects system state.

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 concise, consisting of a single sentence that gets to the point. It is not verbose, though it could benefit from a bit more detail without being overly long.

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 existence of many similar list tools (e.g., vpn_certificate_ca_list, vpn_certificate_local_list), the description lacks sufficient context for an AI agent to distinguish when to use this specific tool. The presence of an output schema is noted, but the description does not elaborate on what is returned.

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 high coverage (100%) with a single 'vdom' parameter fully described. The description adds no additional meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 (list) and the resource (OCSP server configurations) with a purpose (certificate revocation checking). However, it does not differentiate from sibling tools like vpn_certificate_ca_list or vpn_certificate_local_list, which also list certificate-related configurations.

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, such as other certificate list tools or more general search tools. There is no indication of prerequisites or context.

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