ise_mnt_session_delete_by_mac

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

The [DESTRUCTIVE] tag and description clearly flag this as a destructive operation, and it discloses that a server-side operator toggle (CISCO_ISE_MCP_ALLOW_DESTRUCTIVE=1) is required, which adds real behavioral context beyond the schema. No annotations are provided, so the description carries the full burden and does disclose the destructive nature and returns raw XML. However, it doesn't describe what happens on failure (e.g., when no session matches the MAC) or side effects beyond record deletion.

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 compact sentence that packs the essential information: destructive flag, resource type, action verb, endpoint path, and return format. Zero waste, front-loaded with the destructive warning. Appropriate length for the tool's complexity.

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 has 3 params (all documented), no output schema, and no annotations. The description covers purpose, destructive nature, endpoint, and return format. It's reasonably complete for a simple delete operation, but lacks detail on edge-case behavior (no matching session, output format specifics). Given the destructive nature and the existence of a sibling delete-by-id tool, slightly more context would strengthen it.

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 the schema documents all three parameters. The description itself adds the confirm-required-for-destructive context and deployment target details via schema descriptions. The description adds modest value (confirm semantics, deployment resolution) beyond the raw schema, but this is mostly carried by the schema fields. Baseline 3 applies since coverage is high.

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+scope: 'Delete session record by MAC address' with the exact endpoint path and return format (raw XML). It clearly distinguishes from sibling tools like ise_mnt_session_delete_by_id (by ID) and read-only session tools. Loses a point because it doesn't explicitly contrast with the by-ID deletion sibling.

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 [DESTRUCTIVE] tag and the confirm parameter explanation give clear context on when/how to invoke. The description effectively states the precondition (confirm=true, and operator must enable destructive tools). However, it doesn't explicitly say when NOT to use this vs. the by-ID variant, though the by-MAC naming is fairly self-explanatory.

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