ise_openapi_cert_system_import

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It is a mutation operation (POST import) but does not disclose any behavioral traits: no mention of whether existing certificates get replaced, whether overwrite occurs, password requirements for PKCS12, or what happens on conflict. No output/response behavior described.

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 with a trailing API endpoint reference. However, it is essentially a restatement of the endpoint path and name — it adds little beyond what the tool name and title convey. It is compact but sacrifices useful information (purpose beyond 'import', payload details) 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 has a nested 'data' object parameter with 100% schema coverage but no schema structure shown for the import payload in the description. There is no output schema, no mutation-behavior disclosure (no annotations), and the description does not explain what the data body must contain for a successful system certificate import. For a security-sensitive write operation, this is significantly under-specified.

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 adds minimal benefit: 'data' is documented as 'JSON request body' but the description does not explain what fields the import body must contain (e.g., name, cert, privateKey, password, allowOutOfDateCert). The deployment parameter is documented only in the schema. The description does not compensate for the nested-object complexity of the data parameter.

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+resource ('Import system certificate in Cisco ISE') and references the specific API endpoint (POST /api/v1/certs/system-certificate/import). The [Certificates] prefix groups it with other certificate tools, and the name distinguishes it from export/list/delete siblings.

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 provides no explicit guidance on when to use this tool vs alternatives like ise_openapi_cert_trusted_import or ise_openapi_cert_system_list. The [Certificates] prefix and 'system certificate' wording imply a category, but there is no mention of when to choose system vs trusted certificate import, nor prerequisites (e.g., having a PEM/PKCS12 payload ready).

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