ise_openapi_hotpatch_install

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It reveals it's a mutation ('install') operation on a live ISE node, which implies potential service impact, but doesn't mention prerequisites (e.g., a hotpatch file must exist/be uploaded first), side effects (node restart?), whether the operation is asynchronous (likely given ISE's task model), or how to check status. For a state-changing operation on network infrastructure, this is a significant transparency gap.

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 main description is a single concise sentence with the endpoint noted. The parameter descriptions are compact and information-dense. No wasted words. Could arguably include a bit more behavioral context, but what's present is tight.

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 mutating infrastructure operation with no annotations, no output schema, and a nested 'data' object with zero field documentation, the description is incomplete. It doesn't explain return values/asynchronous task semantics, prerequisites (hotpatch must be uploaded), or the role of the 'data' body. The deployment parameter is well-handled, but the core operation semantics are under-specified. Sibling tools like ise_openapi_task_get exist for task tracking, but this isn't referenced.

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 both parameters. The deployment parameter description adds meaningful context ('name, slug, or number', 'Omit to use the only/default deployment', pointing to ise_list_deployments), which goes beyond schema. However, the critical 'data' parameter is only described as 'JSON request body' with no field-level detail about what hotpatch install requires, leaving the agent guessing. Baseline 3 for full coverage, with partial compensation.

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 the verb ('Trigger hotpatch installation') and resource ('on Cisco ISE node'), plus the exact API endpoint. It distinguishes it from sibling tools like ise_openapi_hotpatch_list and ise_openapi_hotpatch_rollback by specifying the 'install' action. The '[Patch]' prefix hints at operational context. It's clear, though it doesn't explicitly contrast with the similar patch_install 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 description doesn't state when to use this tool versus alternatives, but the deployment parameter description provides useful context, explaining how to specify the target deployment and pointing to ise_list_deployments for choices. No explicit when-not-to-use guidance is given, and it doesn't clarify how this differs from the sibling ise_openapi_patch_install (hotpatch vs patch) beyond the name.

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