Add a folder to a collection

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

The description discloses important behavioral details beyond the annotations: the operation is a write, it snapshots the previous state, it supports dry_run, and it can be reverted with nuvio_undo. This provides strong transparency about side effects and recovery, especially valuable because the annotations do not convey these specifics.

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 compact and front-loaded: it states the core operation first, then the supporting behaviors. Every sentence adds value, with no filler or repeated schema information.

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 essential prerequisites, side effects, and rollback path needed to invoke the tool correctly. Since there is no output schema, a brief statement about the return value on success or the audit behavior would improve completeness, but this is a minor gap given the tool's straightforward add operation.

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 25% because only dry_run has a description. The description adds some meaning by noting the folder carries catalog sources and that the collection already exists, but it does not compensate for the lack of descriptions for collection_id, profile_id, or the folder object's fields beyond what their names suggest. The schema structure provides partial clarity, but the remaining gaps keep this at a minimally adequate level.

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 ('Append') and resource ('a folder with catalog sources to an existing collection'), clearly distinguishing this from sibling tools like update_collection_folder, remove_collection_folder, or create_collection. The addition of 'existing collection' reinforces what action is being performed.

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 clearly indicates when to use the tool: when appending a folder to an already existing collection. It does not explicitly name alternatives or state when not to use it, but the operation and prerequisite are unambiguous enough for correct selection.

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