ise_openapi_cert_trusted_import

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

No annotations were provided, so the description must carry the full behavioral burden. 'import' implies a write operation, but nothing discloses side effects (e.g., whether the certificate immediately becomes trusted, whether it overwrites, whether admin/root privileges are required for cert management in ISE). The truststore is a security-sensitive target; the description doesn't warn about impact or reversibility.

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, efficient line with the API endpoint embedded, which is useful. No padding or redundancy. It front-loads the primary purpose clearly. Minor point: the '[Certificates]' prefix is redundant with sibling names but harmless.

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?

This is a mutation tool (import into truststore) with no annotations and no output schema, and the critical 'data' parameter is left as an opaque JSON body. The description explains neither the required certificate payload structure nor side effects. For a security-sensitive certificate operation, this is meaningfully incomplete compared to what a capable agent needs.

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 both parameters (data and deployment) have schema descriptions. The 'data' object is opaque ('JSON request body') with no field-level explanation of what must be included for certificate import (e.g., cert contents, format, friendly name). The deployment param is well-documented in the schema, so the description adds nothing beyond it.

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 a specific verb+resource: 'Add root certificate to the Cisco ISE truststore' with the API endpoint. It clearly distinguishes from siblings like ise_openapi_cert_trusted_list/get/delete. However, it doesn't fully distinguish from the related system-certificate import (ise_openapi_cert_system_import) which could be confused.

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 identifies the category ('[Certificates]') and endpoint but provides no explicit when-to-use guidance or mention of alternatives. The deployment parameter references ise_list_deployments for selection, which gives some context. No exclusions or warnings about when NOT to use this tool versus system cert import.

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