qlikcloud_delete

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

With no annotations provided, the description fully carries the transparency burden. It discloses that deletion moves items to the Recycle Bin, that permanent deletion is impossible, that Spaces are blocked, and that already-recycled items are refused outright.

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 well-structured with bullets and an IMPORTANT callout, but some phrasing is redundant (e.g., 'with exactly their permissions: you can only retire resources you are allowed to move' and the repetitive admin wording). Still, the extra detail is mostly purposeful.

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?

The description covers the operation's side effects, limitations, required user confirmation, and unsupported cases. Since an output schema exists, omitting return-value details is acceptable, and nothing critical is missing for correct invocation.

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?

The schema only says 'Path' with no description, so the tool description must compensate. It does so by giving an example path, listing supported path prefixes, and stating which resource types are accepted or rejected.

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 tool deletes a Qlik Cloud resource at a given API path, and enumerates exactly which resource types are supported, blocked, or unsupported. This distinguishes it from sibling tools like get, login, and health.

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 provides explicit usage guidance: tell the user what will be deleted and wait for confirmation before calling. It also explains when deletion is blocked (spaces, already-recycled items) and that no alternative deletion route exists.

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