ise_ers_request

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

Although no annotations are provided, the description itself carries the [DESTRUCTIVE] marker and the confirm parameter schema explicitly explains that the server requires destructive tool enabling (CISCO_ISE_MCP_ALLOW_DESTRUCTIVE=1) plus confirm=true. This is excellent disclosure of mutation behavior, auth requirements, and failure-refusal conditions beyond what annotations would provide.

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 tight sentence that packs the destructive warning, raw-passthrough nature, coverage scope, and a concrete path example. Zero wasted words, all high-value information.

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 generic passthrough tool with no output schema and 6 params (2 required), the description plus rich schema adequately covers semantics: path convention, safety requirements, deployment targeting. The confirm/deployment/params/data semantics are all covered by the schema. Returns are not documented, but for a raw passthrough that's acceptable since response shape is inherently tool-dependent.

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 83% and the schema already thoroughly documents each parameter (path example, method enum, data, params, confirm safety semantics, deployment selection). The description adds the relative-to-host-root detail for path semantics. With such high schema coverage, baseline 3 is appropriate; the description works with the schema rather than needing to compensate heavily.

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 this is a 'Raw ERS passthrough' for action sub-paths not covered by typed tools, with a concrete example ('POST ers/config/endpoint/{id}/deregister') and specifies the path is relative to host root. This clearly differentiates it from the many typed ise_ers_* siblings.

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 explicitly says it's for 'action sub-paths not covered by a typed tool' (e.g. deregister), which tells the agent when to use it versus the typed alternatives. However, it doesn't explicitly list when NOT to use it (e.g., prefer typed tools when they exist), though this is strongly implied by the sibling naming pattern.

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