ise_openapi_cert_system_list

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

No annotations are provided, so the description carries the burden. It is a read operation (list/get) which is implicitly clear from the verb and endpoint. It doesn't describe return format, pagination behavior, or whether a particular node is required to be a specific type (e.g., PSN vs PAN). For a simple GET list operation, the behavioral traits are reasonably inferable, though more detail on output would help.

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 compact—a single sentence with the endpoint reference and category tag. It's front-loaded with the core purpose. No waste, though it could arguably be slightly expanded on usage without harming conciseness.

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?

For a simple list operation with one required parameter and full schema coverage, the description covers the essentials: what it does, the resource type, and the required node context. It lacks note on return format (array of certificate details), which would aid an agent, but given no output schema and the read-only nature, it's reasonably complete for the tool's simplicity.

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%. The hostName parameter is described only as 'Path parameter hostName' in the schema, and the description contextualizes it as the node whose system certificates are listed. The deployment parameter is well-documented in the schema with concrete examples and guidance to call ise_list_deployments. The description adds the node-scoping context for hostName beyond the schema's terse path-parameter note.

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 tool lists all system certificates for a particular node, with a specific verb (list/get) and resource (system certificates by host). It names the exact endpoint and requires a hostName. It doesn't explicitly distinguish from siblings like ise_openapi_cert_system_get, though the 'list' vs 'get' wording and 'particular node' scoping help, and the '[Certificates]' tag groups it appropriately.

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 states it lists certificates for a specific node, implying you need to know the hostName first. There's no explicit guidance on when to use this vs ise_openapi_cert_system_get (for a single cert) or ise_openapi_cert_trusted_list (for trusted certs). The deployment parameter description does reference calling ise_list_deployments for choices, which is helpful context, but the main description lacks alternative-tool guidance.

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