ise_openapi_cert_trusted_delete

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

No annotations are provided, so the description carries the burden. The [DESTRUCTIVE] tag and the confirm parameter description clearly disclose that this is an irreversible operation requiring explicit confirmation and an environment variable (CISCO_ISE_MCP_ALLOW_DESTRUCTIVE=1). This is strong behavioral disclosure for a destructive tool, though it doesn't detail what the response returns or downstream impact of deleting a cert.

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?

Single line with clear tags and endpoint reference. Compact and front-loaded with the DESTRUCTIVE warning. No wasted words, though it conflates multiple pieces of info without line breaks.

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's complexity is moderate (3 params, 1 required, no nested objects, no output schema). The description plus schema covers the purpose, destructive nature, confirmation gate, and deployment targeting. Given no output schema and a destructive operation, slightly more detail on result/return would help but the essential information is present.

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%, so the schema documents all three params. The description itself doesn't add parameter meaning, but the schema descriptions are rich, especially for confirm (explaining the destructive gate and env var) and deployment (multiple accepted formats and pointer to ise_list_deployments). The id param is minimal (just 'Path parameter'), which could be improved but is understandable.

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 (Delete), resource (trusted certificate), and identifies by ID with the HTTP endpoint shown. The [Certificates] tag distinguishes it from system/csr cert operations, though the sibling set includes several cert tools, so the scope distinction is somewhat implicit.

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 names the exact resource type and ID-based selection. The confirm requirement and deployment targeting are explained in the schema descriptions. However, there's no explicit when-to-use vs alternatives (e.g., when to delete vs update a trusted cert), no mention that deletion is irreversible beyond the [DESTRUCTIVE] tag, and no statement of when not to use this tool.

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