ise_openapi_cert_system_export

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

No annotations are provided, so the description carries full burden. It doesn't disclose what the export returns (file? base64? format like PEM/PKCS12?), whether a passphrase is required for private keys, authentication requirements, or side effects. The endpoint path is given but behavioral details about the export output format are absent, which is significant for an export operation.

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 sentence that efficiently conveys the operation and endpoint. It's front-loaded with the purpose. No wasted words, though it could be slightly more generous with behavioral detail without becoming verbose.

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 moderately complex operation: a POST export with a nested 'data' object and deployment targeting. There's no output schema to explain return format, no annotations, and the nested 'data' object is opaque. Given the sibling set includes related cert operations (get, list, delete, import), the description could clarify what distinguishes an export from a get, and what artifact the user receives. The deployment logic adds complexity that the description handles, but the overall completeness for a write/export operation with unknown output format is insufficient.

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%, with descriptions for both data (JSON request body) and deployment (target deployment with examples). The deployment parameter is well-explained with format examples and a reference to ise_list_deployments. However, the 'data' parameter that presumably contains the certificate ID is just described as 'JSON request body' with no schema of its fields, so the description adds no detail about what goes inside it. The description mentions 'certificate ID' but the parameter semantics for the crucial data object remain opaque.

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 ('export a system certificate') with a specific resource (system certificate) and the endpoint (POST /api/v1/certs/system-certificate/export). The [Certificates] prefix helps categorize it among siblings. It doesn't explicitly distinguish from siblings like import/list/get/delete, but the verb 'export' and resource scope are clear.

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 implies usage: to export a system certificate by ID. The deployment parameter description provides useful guidance on how to select a target deployment and references ise_list_deployments for choices. However, it doesn't explicitly state when NOT to use this tool versus alternatives like ise_openapi_cert_system_get (which retrieves but doesn't export), nor what format the export produces.

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