ise_openapi_radius_policy_set_delete

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

The description prominently marks this as [DESTRUCTIVE], which is critical behavioral disclosure. While no annotations are provided (so the description carries the full burden), the confirm parameter and deployment parameters add meaningful context about the destructive nature, the operator-level requirement (CISCO_ISE_MCP_ALLOW_DESTRUCTIVE=1), and target deployment selection. This is strong transparency for a destructive operation with zero annotation coverage.

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?

Extremely concise description - a single line that includes the destructive warning, policy scope, verb+resource, and the HTTP endpoint. Every element serves a purpose and it's front-loaded with the most critical information ([DESTRUCTIVE]).

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?

For a destructive operation with no annotations and no output schema, this description does a solid job: it flags destructiveness, explains the safety gating (confirm + operator flag), and covers deployment targeting. The main gap is that it doesn't warn about irreversibility or cascading effects (e.g., what happens to authentication policies tied to the deleted policy set). But given the richness of the schema parameters covering confirm and deployment, it's reasonably complete.

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 already documents all three parameters (id, confirm, deployment). The description adds value by explaining the confirm parameter's destructive requirement and the deployment parameter's format options, which goes somewhat beyond the schema. However, the description doesn't explain the id parameter format or what makes a valid policy set id. Baseline 3 is appropriate.

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 it deletes a policy set for Network Access via the DELETE endpoint, with a specific RESTful verb and path. However, it doesn't differentiate from the analogous ise_openapi_tacacs_policy_set_delete sibling (Network Access vs TACACS is implied but not explicit), though the '[Policy: Network Access]' prefix provides some distinction.

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 when to use this tool (deleting a Network Access policy set) but provides no explicit guidance on when NOT to use it or alternatives. The deployment parameter description references ise_list_deployments, which is helpful context. However, no exclusions or alternatives (like the ERS delete or TACACS variant) are mentioned.

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