ise_openapi_request

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

The description goes beyond annotations (which are absent entirely) by prominently marking the tool as [DESTRUCTIVE] and explaining the confirm=true requirement plus the CISCO_ISE_MCP_ALLOW_DESTRUCTIVE=1 server-side gate. This is strong disclosure of the destructive operation behavior and the confirm mechanism requirements. It doesn't detail error handling or response format, but the destructive safety profile is well covered.

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 efficient and front-loaded with the [DESTRUCTIVE] warning, which is appropriately prioritized. It packs purpose, usage scope, example, and spec reference into two sentences without fluff. Slightly more behavioral detail about execution preconditions would be beneficial but the structure is sound.

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 raw passthrough tool with no output schema, the description conveys the essential context: it's a generic escape hatch, requires method+path, and needs an example. The confirm field and deployment guidance are documented in the schema. It's complete enough for an agent to invoke this correctly, though it could note that responses follow OpenAPI spec conventions.

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 83%, so most parameters (path, method, confirm, deployment) are already documented in the schema. The description adds the confirm requirement detail and deployment semantics in the schema. The description text itself adds the example path format ('/api/v1/certs/system-certificate/<host>') which aids understanding. With high schema coverage, 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 is a 'Raw Open API passthrough — call ANY /api/ endpoint not covered by a typed tool.' It specifies the verb (call), resource (any /api/ endpoint), and the key scoping that distinguishes it from the many typed sibling tools. The example path and live spec URL further clarify intent.

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 frames this as the fallback for endpoints 'not covered by a typed tool,' which is clear usage guidance. It names the deployment selection option and points to ise_list_deployments. It does not explicitly list when NOT to use it or name specific alternatives, but the sibling set (typed ise_openapi_* tools) makes the distinction reasonably inferable.

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