Delete a collection

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the destructive nature is known. The description adds valuable context beyond this: the previous state is snapshotted before the write and can be reverted with nuvio_undo. This gives an agent a concretely safe recovery path.

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 two short sentences with no filler. The primary action is front-loaded, and the recovery mechanism is placed immediately after, making it easy for an agent to parse both the purpose and the safety behavior quickly.

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 destructive tool with no output schema, the description plus annotations covers the essentials: what is deleted, that it is destructive, and how to revert. The confirm-to-execute behavior is documented in the schema's confirm description, so the agent can discover it. It could mention the preview-without-confirm behavior in prose, but the schema already covers that.

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 only 33%; only the confirm parameter is documented in the schema. The description does not compensate for this: it does not explain the role of profile_id, the meaning of collection_id beyond the obvious, or that confirm must be true to perform the destructive write. 'From a profile' hints at profile_id, but this is far from adequate 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 states a specific verb and resource: 'Remove a collection from a profile.' It clearly distinguishes this from sibling collection operations like update, create, duplicate, or remove_collection_folder, and the profile scoping adds useful precision.

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 implies when to use the tool: when you need to delete a collection from a profile. It also adds the useful note that the operation is reversible via nuvio_undo. However, it does not explicitly mention alternatives or exclusion cases, such as using nuvio_remove_collection_folder for folders or nuvio_update_collection for modifications.

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