ise_openapi_repo_delete

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

While no annotations are provided, the description explicitly marks this as DESTRUCTIVE and prominently describes the confirm=true requirement and the operator-level enablement (CISCO_ISE_MCP_ALLOW_DESTRUCTIVE=1). This is substantial behavioral disclosure about the safety gate beyond what the raw schema reveals, genuinely useful for the agent.

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 compact — a single line plus effective schema param descriptions. The confirm param explanation is thorough without being verbose. Front-loaded with the DESTRUCTIVE tag. Slight redundancy: '[DESTRUCTIVE]' tag plus the confirm language is repeated across schema and description, but it's warranted given the stakes.

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 destructive mutation with no annotations and no output schema, so the description carries a heavier burden. It adequately covers the safety gate, the endpoint path, and deployment targeting. It doesn't mention what happens to associated files or whether deletion is reversible, and doesn't describe the response, but for a simple repo deletion the core safety and targeting context is well covered.

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 baseline is 3, but the description adds significant value beyond the schema on the confirm parameter by explaining the two-layered protection (caller must set true AND operator must enable destructive mode) and on deployment by giving concrete formats ('RADIUS Only', 'radius-only', '1') and pointing to ise_list_deployments. The name param is minimally documented but self-explanatory.

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 'Delete a specific repository' with the DELETE endpoint, which is a clear verb+resource. However, 'repository' is a somewhat generic term and the description doesn't differentiate this from the many sibling delete tools (e.g., ise_ers_delete, ise_openapi_cert_system_delete). The scope is clear but sibling distinction depends on the '[Repository]' tag.

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 context through the '[DESTRUCTIVE]' tag and shows the HTTP endpoint, but doesn't explicitly state when to use this vs alternatives like ise_openapi_repo_list/get/update. No when-not-to-use guidance, no prerequisites mentioned beyond the confirm requirement which is actually in the schema.

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