ise_ers_delete

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

No annotations are provided, so the description carries the full burden. It explicitly marks the [DESTRUCTIVE] nature, and the confirm parameter's schema discloses that an operator must enable destructive tools via environment variable CISCO_ISE_MCP_ALLOW_DESTRUCTIVE=1 or the call is refused. This is substantial behavioral context for a destructive operation, revealing the confirmation gate and the operator-level toggle requirement.

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 extremely concise at one short sentence. It front-loads the destructive warning. It is appropriately sized for a tool fully documented via its schema. No wasted words, though it could arguably include one line about irreversibility given it's a delete operation.

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?

Given it's a destructive mutation with high schema coverage (75%) and no output schema (delete typically returns minimal), the description plus schema adequately cover id, resource selection, confirm gating, and deployment targeting. The main gaps are: no explicit warning that deletion is irreversible/lossy, and no mention of return/response behavior. Given the confirm gate and resource pointer, this is reasonably complete for its class.

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 75%, which is high. The description itself says 'by ID' clarifying the id parameter's role. The confirm parameter's schema adds behavioral semantics (must be true to execute, env var gate). The resource parameter schema points to ise_ers_resources for enumeration. The description does not add detail on id format (e.g., UUID vs name), but with 75% coverage the schema carries the burden; description adds modest value.

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 "Delete an ERS object by ID" clearly states the verb (delete), resource type (ERS object), and key qualifier (by ID). This clearly differentiates it from sibling tools like ise_ers_get (retrieve) and ise_ers_create (create). The [DESTRUCTIVE] prefix adds emphasis. However, it doesn't explicitly distinguish it from ise_ers_patch/update beyond the naming, though purpose is 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 use when deleting by ID, and the resource parameter explicitly points to ise_ers_resources for supported operations. The confirm parameter schema explains the destructive activation requirement (CISCO_ISE_MCP_ALLOW_DESTRUCTIVE=1). However, it doesn't explicitly state when NOT to use it or mention alternatives (e.g., ise_ers_patch for partial updates), nor warn against deleting protected resources.

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