ise_openapi_backup_cancel

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

With no annotations provided, the description carries the full behavioral disclosure burden. It does not say whether the tool requires an in-progress backup (error if none running), whether cancellation is immediately effective or asynchronous, what happens to partially-written backup files, or what the response contains. As a mutating operation with zero annotation coverage, this is a notable 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 description is a compact single sentence that names the action, category, and underlying endpoint. It's front-loaded and has zero waste. Losing a point only because it could add brief behavioral context (e.g., error conditions) without becoming verbose.

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?

Given this is a mutating action tool with no annotations and no output schema, the description is somewhat thin. The deployment parameter delegation to ise_list_deployments is a helpful pointer. However, for a cancel operation, critical context is missing: what happens if no backup is running, how to confirm cancellation success, and the contents of the required 'data' body. The tool is simple enough that this isn't severely deficient, but it leaves important behavioral gaps.

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 100%, and the two parameters (data, deployment) are documented in the schema. The description adds no additional meaning about the 'data' field format or what the cancel operation requires in the request body. The deployment parameter is well-described in the schema itself. Baseline 3 is appropriate given high schema coverage, but the description adds nothing beyond the schema.

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+resource: 'Cancel the running backup' via POST /api/v1/backup-restore/config/cancel-backup. It's distinct from sibling backup tools (backup_create, backup_restore, backup_last_status) by targeting a running backup operation. The [Backup & Restore] tag adds category context.

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 identifies when to use it (to cancel a running backup), which is distinct from backup_create and backup_restore siblings. However, it doesn't explicitly state when NOT to use it or whether it requires an active backup to be present, nor does it reference checking backup_last_status first to confirm a backup is running. Guidance is implicit rather than explicit.

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