Create a collection

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

The description discloses a meaningful behavioral trait beyond the annotations: the previous state is snapshotted before the write and can be reverted with nuvio_undo. This complements the destructiveHint=false annotation by explaining why the operation is safe, and it usefully names the recovery path. It does not cover failure or conflict behavior (e.g., duplicate collection id), so it is strong but not exhaustive.

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?

Two sentences with zero waste: the first states the primary action and target, the second adds the critical snapshot/undo caveat. It is front-loaded with purpose and every sentence earns its place.

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 non-idempotent write operation with a nested object parameter and no output schema, the description covers the essential purpose and the key undo safeguard, but omits return-value expectations and behavior on repeated calls or duplicate ids. Given the tool's complexity, an agent would still have open questions about what to expect after 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?

Schema description coverage is 0%, so the description must compensate, but it only adds minimal meaning: the phrase 'to a profile' clarifies that profile_id identifies the target profile. The large nested collection object, its required id/title fields, and the defaults (profile_id default 1, max 6) receive no explanatory help, leaving the agent to infer semantics from property names and enums alone.

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 ('Add'), resource ('collection'), and target scope ('to a profile'), clearly differentiating creation from siblings like nuvio_update_collection, nuvio_delete_collection, and nuvio_list_collections. It is clear and unambiguous, though it does not explicitly name any sibling it is not, which keeps it just short of a 5.

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?

Usage context is implied rather than stated: 'Add a new collection' suggests it is the tool for creating collections as opposed to updating or duplicating them (nuvio_update_collection, nuvio_duplicate_collection). No explicit when-to-use or when-not-to-use guidance, and no prerequisites such as the profile needing to exist, are provided.

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